Quantcast
Channel: Linux | Kernel
Viewing all 165258 articles
Browse latest View live

[PATCH 0/3] Support persistent memory as reserved type in e820/EFI

$
0
0
ACPI 6.0 defines persistent memory ranges in multiple firmware interfaces, E820_PMEM type in e820, EFI_PERSISTENT_MEMORY type in EFI, and ACPI NFIT ta

[PATCH 1/3] resource: Make __request_region to inherit from immediate parent

$
0
0
__request_region() sets 'flags' from a given 'parent' to inherit its attribute. When a target resource has conflict, this function inserts a resource

[PATCH 2/3] resource: Add iomem_set_desc() to set I/O descriptor

$
0
0
ACPI 6.0 defines persistent memory ranges in multiple firmware interfaces, E820_PMEM type in e820, EFI_PERSISTENT_MEMORY type in EFI, and ACPI NFIT ta

[PATCH 3/3] ACPI: Change NFIT driver to set PMEM type to iomem entry

$
0
0
Change acpi_nfit_register_region() to call iomem_set_desc() with IORES_DESC_PERSISTENT_MEMORY for NFIT_SPA_PM ranges found in ACPI NFIT table. When F

[PATCH] scripts/dtc: dtx_diff - add info to error message

$
0
0
From: Frank Rowand <frank.rowand@sonymobile.com> If kernel config options are not properly set, "make scripts" will not compile dtc. Update the unab

[PATCH 0/3] PCI: Clean up warnings

$
0
0
I'm on a quest to clean up compiler warnings in drivers/pci. I'd like to be able to treat warnings as errors, at least for the 0day build robot. ---

[PATCH 1/3] PCI: Check device_attach() return value always

$
0
0
Previously we checked the device_attach() return value only when CONFIG_BUG=y. That caused this warning in builds where CONFIG_BUG is not set: dri

[PATCH 2/3] PCI/PME: Remove redundant port lookup

$
0
0
We've already looked up srv->port a few lines earlier, and there's no need to do it again. Remove the redundant lookup. Signed-off-by: Bjorn Helgaas

[PATCH 3/3] PCI/PME: Restructure pcie_pme_suspend() to prevent compiler warning

$
0
0
Previously we had this: if (wakeup) ret = enable_irq_wake(...); if (!wakeup || ret) ... "ret" is only evaluated when "wakeup" is true, a

[PATCH] Staging:octeon:removed blank line after {

$
0
0
Removed blank line after curly braces. Found using checkpatch.pl. Signed-off-by: Bhumika Goyal <bhumirks@gmail.com> --- drivers/staging/octeon/ether

[PATCH 0/5] Clean up warnings (part 2, asm/pci-bridge.h)

$
0
0
We've had some non-arch-specific stuff (pci_has_flag() and associated definitions like PCI_PROBE_ONLY) in asm/pci-bridge.h. This leads to warnings li

[PATCH 1/5] PCI: Move pci_set_flags() from asm-generic/pci-bridge.h to linux/pci.h

$
0
0
The PCI flag management constants and functions were previously declared in include/asm-generic/pci-bridge.h. But they are not specific to bridges, a

[PATCH 2/5] PCI: Remove includes of empty asm-generic/pci-bridge.h

$
0
0
include/asm-generic/pci-bridge.h is now empty, so remove every #include of it. Signed-off-by: Bjorn Helgaas <bhelgaas@google.com> --- arch/alpha/inc

[PATCH 3/5] ARM64: PCI: Remove generated include of asm-generic/pci-bridge.h

$
0
0
arm64 generates asm/pci-bridge.h, which merely includes the now-empty asm-generic/pci-bridge.h. Stop generating asm/pci-bridge.h, and stop including

[PATCH 4/5] PCI: Remove empty asm-generic/pci-bridge.h

$
0
0
include/asm-generic/pci-bridge.h is empty, and nobody includes it, so remove it. Signed-off-by: Bjorn Helgaas <bhelgaas@google.com> --- include/asm-

[PATCH 5/5] PCI: Remove includes of asm/pci-bridge.h

$
0
0
Drivers should include asm/pci-bridge.h only when they need the arch- specific things provided there. Outside of the arch/ directories, the only driv

[PATCH v8 0/6] cpufreq: powernv: Redesign the presentation of throttle notification and solve bug-fixes in the driver

$
0
0
In POWER8, OCC(On-Chip-Controller) can throttle the frequency of the CPU when the chip crosses its thermal and power limits. Currently, powernv-cpufre

[PATCH v8 1/6] cpufreq: powernv: Free 'chips' on module exit

$
0
0
This will free the dynamically allocated memory of 'chips' on module exit. Signed-off-by: Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com> Reviewed-

[PATCH v8 2/6] cpufreq: powernv: Hot-plug safe the kworker thread

$
0
0
In the kworker_thread powernv_cpufreq_work_fn(), we can end up sending an IPI to a cpu going offline. This is a rare corner case which is fixed using

[PATCH v8 3/6] cpufreq: powernv: Remove cpu_to_chip_id() from hot-path

$
0
0
cpu_to_chip_id() does a DT walk through to find out the chip id by taking a contended device tree lock. This adds an unnecessary overhead in a hot pat
Viewing all 165258 articles
Browse latest View live


Latest Images