Re: [PATCH 2/2] staging: rtl8723au:core

On Mon, 2014-10-27 at 06:45 +0100, Jes Sorensen wrote: > Joe Perches writes: > > On Sun, 2014-10-26 at 16:18 +, Paul McQuade wrote: > >> ERROR: spaces required around that ':' (ctx:VxE) [] > >> diff --git a/drivers/staging/rtl8723au/core/rtw_ieee80211.c > >>

[PATCH RFC 04/12] time: Add rtc_tm_to_time() safe version(using time64_t)

The kernel uses 32-bit signed value(time_t) for seconds since 1970-01-01:00:00:00, thus it will overflow at 2038-01-19 03:14:08 on 32-bit systems. We call this "2038 safety" issue. As part of addressing 2038 saftey for in-kernel uses, this patch adds the safe rtc_tm_to_time() using time64_t.

[PATCH RFC 06/12] time: Fix build warnings for time64_t to __kernel_time_t warning on 64-bit systems.

The kernel uses 32-bit signed value(time_t) for seconds since 1970-01-01:00:00:00, so it will overflow at 2038-01-19 03:14:08 on 32-bit systems. We call this "2038 safety" issue. This patch fixed the build warnings brought by former patches. Signed-off-by: pang.xunlei ---

[PATCH RFC 09/12] time: Convert rtc_time_to_tm_unsafe() to rtc_time_to_tm() in alarm_set_rtc()

The kernel uses 32-bit signed value(time_t) for seconds since 1970-01-01:00:00:00, so it will overflow at 2038-01-19 03:14:08 on 32-bit systems. We call this "2038 safety" issue. As part of addressing 2038 saftey for in-kernel uses, this patch creates no functional change in existing users,

[PATCH RFC 11/12] time: Convert xen_read_wallclock() to use timespec64

The kernel uses 32-bit signed value(time_t) for seconds since 1970-01-01:00:00:00, so it will overflow at 2038-01-19 03:14:08 on 32-bit systems. We call this "2038 safety" issue. As part of addressing 2038 safety for in-kernel uses, this patch creates no functional change in existing users,

[PATCH RFC 12/12] time: Convert pvclock_read_wallclock() to use timespec64

The kernel uses 32-bit signed value(time_t) for seconds since 1970-01-01:00:00:00, so it will overflow at 2038-01-19 03:14:08 on 32-bit systems. We call this "2038 safety" issue. As part of addressing 2038 safety for in-kernel uses, this patch creates no functional change in existing users,

[PATCH RFC 08/12] time: Add rtc_time_to_tm() safe version(using time64_t)

The kernel uses 32-bit signed value(time_t) for seconds since 1970-01-01:00:00:00, thus it will overflow at 2038-01-19 03:14:08 on 32-bit systems. We call this "2038 safety" issue. As part of addressing 2038 saftey for in-kernel uses, this patch adds the safe rtc_time_to_tm() using time64_t.

[PATCH RFC 05/12] time: Convert rtc_tm_to_time_unsafe() to rtc_tm_to_time() in rtc_hctosys()

The kernel uses 32-bit signed value(time_t) for seconds since 1970-01-01:00:00:00, so it will overflow at 2038-01-19 03:14:08 on 32-bit systems. We call this "2038 safety" issue. As part of addressing 2038 saftey for in-kernel uses, this patch creates no functional change in existing users,

[PATCH RFC 07/12] time: Rename rtc_time_to_tm() to rtc_time_to_tm_unsafe()

The kernel uses 32-bit signed value(time_t) for seconds since 1970-01-01:00:00:00, thus it will overflow at 2038-01-19 03:14:08 on 32-bit systems. We call this "2038 safety" issue. Currently, rtc_time_to_tm() deals with "unsigned long" which is 2038 unsafe on 32-bit systems. As part of

[PATCH RFC 02/12] time: Add mktime() safe version(using time64_t)

The kernel uses 32-bit signed value(time_t) for seconds since 1970-01-01:00:00:00, thus it will overflow at 2038-01-19 03:14:08 on 32-bit systems. We call this "2038 safety" issue. As part of addressing 2038 saftey for in-kernel uses, this patch adds the safe mktime() using time64_t. After

[PATCH RFC 10/12] time: Convert do_settimeofday() to use timespec64

The kernel uses 32-bit signed value(time_t) for seconds since 1970-01-01:00:00:00, so it will overflow at 2038-01-19 03:14:08 on 32-bit systems. We call this "2038 safety" issue. As part of addressing 2038 safety for in-kernel uses, convert do_settimeofday() to use the timespec64 structure, and

[PATCH RFC 03/12] time: Rename rtc_tm_to_time() to rtc_tm_to_time_unsafe()

The kernel uses 32-bit signed value(time_t) for seconds since 1970-01-01:00:00:00, thus it will overflow at 2038-01-19 03:14:08 on 32-bit systems. We call this "2038 safety" issue. Currently, rtc_tm_to_time() deals with "unsigned long" which is 2038 unsafe on 32-bit systems. As part of

Re: [PATCH v3] sched/fair: Care divide error in update_task_scan_period()

Could you review my patch? Thanks, Yasuaki Ishimatsu (2014/10/22 16:04), Yasuaki Ishimatsu wrote: > While offling node by hot removing memory, the following divide error > occurs: > >divide error: [#1] SMP >[...] >Call Trace: > [...] handle_mm_fault > [...] ?

[PATCH RFC 01/12] time: Rename mktime() to mktime_unsafe()

The kernel uses 32-bit signed value(time_t) for seconds since 1970-01-01:00:00:00, thus it will overflow at 2038-01-19 03:14:08 on 32-bit systems. We call this "2038 safety" issue. Currently, mktime() deals with "unsigned long" which is 2038 unsafe on 32-bit systems. As part of addressing

Re: [PATCH] staging: rtl8723au: create macro get_max_rate

Paul McQuade writes: > create marco for max_rate values > > Signed-off-by: Paul McQuade > --- > drivers/staging/rtl8723au/core/rtw_ieee80211.c | 58 > -- > 1 file changed, 26 insertions(+), 32 deletions(-) > > diff --git a/drivers/staging/rtl8723au/core/rtw_ieee80211.c

[PATCH RFC 00/12] time: Convert do_settimeofday() to use timespec64

The kernel uses 32-bit signed value(time_t) for seconds since 1970-01-01:00:00:00, so it will overflow at 2038-01-19 03:14:08 on 32-bit systems. We call this "2038 safety" issue. This series doesn't involve any functional change, and mainly converts do_settimeofday() to use timespec64. During

Re: [PATCH 2/2] staging: rtl8723au:core

Joe Perches writes: > On Sun, 2014-10-26 at 16:18 +, Paul McQuade wrote: >> ERROR: spaces required around that ':' (ctx:VxE) >> >> Signed-off-by: Paul McQuade >> --- >> drivers/staging/rtl8723au/core/rtw_ieee80211.c | 16 >> 1 file changed, 8 insertions(+), 8 deletions(-)

[PATCH] MAINTAINERS: Update ivtv mailing lists as subscriber-only

Mark these as subscriber-only mailing lists. Signed-off-by: Joe Perches --- I got rejects not moderation emails for patches to these lists... MAINTAINERS | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/MAINTAINERS b/MAINTAINERS index 1b063fc..2e353c7 100644 ---

[PATCH] checkpatch: Try to avoid mask and shift errors

Shift has a higher precedence that mask so warn when a mask then shift operation is done without parentheses around the mask. This test works well for a right shift, but the left shift is pretty commonly done correctly so only warn on the right shift. Signed-off-by: Joe Perches ---

[PATCH 03/11] aiptek: Fix probable mask then right shift defects

Precedence of & and >> is not the same and is not left to right. shift has higher precedence and should be done after the mask. Here the shifts are unnecessary and a non-zero value can be used as the test to set 1 or zero. Signed-off-by: Joe Perches --- drivers/input/tablet/aiptek.c | 6 +++---

[PATCH 02/11] radeon: evergreen: Fix probable mask then right shift defects

Precedence of & and >> is not the same and is not left to right. shift has higher precedence and should be done after the mask. Add parentheses around the mask. Use the already #defined values instead of hardcoding. Signed-off-by: Joe Perches --- drivers/gpu/drm/radeon/evergreen.c | 3 ++- 1

[PATCH 00/11] treewide: mask then shift defects and style updates

logical mask has lower precedence than shift but should be done before the shift so parentheses are generally required. And when masking with a fixed value after a shift, normal kernel style has the shift on the left, then the shift on the right so convert a few non-conforming uses. Joe Perches

[PATCH 06/11] wm8350-core: Fix probable mask then right shift defect

Precedence of & and >> is not the same and is not left to right. shift has higher precedence and should be done after the mask. Add parentheses around the mask. Signed-off-by: Joe Perches --- drivers/mfd/wm8350-core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 01/11] block: nvme-scsi: Fix probable mask then right shift defects

Precedence of & and >> is not the same and is not left to right. shift has higher precedence and should be done after the mask. Add parentheses around the mask. Signed-off-by: Joe Perches --- drivers/block/nvme-scsi.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff

[PATCH 11/11] sound: ad1889: Fix probable mask then right shift defects

Precedence of & and >> is not the same and is not left to right. shift has higher precedence and should be done after the mask. Add parentheses around the mask. Signed-off-by: Joe Perches --- sound/pci/ad1889.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git

[PATCH 08/11] ssb: driver_chip_comon_pmu: Fix probable mask then right shift defect

Precedence of & and >> is not the same and is not left to right. shift has higher precedence and should be done after the mask. Add parentheses around the mask. Signed-off-by: Joe Perches --- drivers/ssb/driver_chipcommon_pmu.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff

[PATCH 07/11] iwlwifi: dvm: Fix probable mask then right shift defect

Precedence of & and >> is not the same and is not left to right. shift has higher precedence and should be done after the mask. Add parentheses around the mask. Signed-off-by: Joe Perches --- drivers/net/wireless/iwlwifi/dvm/lib.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff

[PATCH 09/11] tty: ipwireless: Fix probable mask then right shift defects

Precedence of & and >> is not the same and is not left to right. shift has higher precedence and should be done after the mask. Add parentheses around the masks. Signed-off-by: Joe Perches --- drivers/tty/ipwireless/hardware.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-)

[PATCH 10/11] hwa-hc: Fix probable mask then right shift defect

Precedence of & and >> is not the same and is not left to right. shift has higher precedence and should be done after the mask. Add parentheses around the mask. Signed-off-by: Joe Perches --- drivers/usb/host/hwa-hc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 05/11] cx25840/cx18: Use standard ordering of mask and shift

Precedence of & and >> is not the same and is not left to right. shift has higher precedence and should be done after the mask. This use has a mask then shift which is not the normal style. Move the shift before the mask to match nearly all the other uses in kernel. Signed-off-by: Joe Perches

[PATCH 04/11] dvb-net: Fix probable mask then right shift defects

Precedence of & and >> is not the same and is not left to right. shift has higher precedence and should be done after the mask. Add parentheses around the mask. Signed-off-by: Joe Perches --- drivers/media/dvb-core/dvb_net.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git

[Patch v7 06/18] ACPI: Fix minor syntax issues in processor_core.c

Fix minor syntax issues in processor_core.c to follow coding styles. Signed-off-by: Jiang Liu --- drivers/acpi/processor_core.c |9 - 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/drivers/acpi/processor_core.c b/drivers/acpi/processor_core.c index

[Patch v7 16/18] x86, irq, ACPI: Implement interfaces to support ACPI based IOAPIC hot-removal

Implement acpi_unregister_ioapic() to support ACPI based IOAPIC hot-removal. An IOAPIC could only be removed when all its pins are unused. Signed-off-by: Jiang Liu --- arch/x86/include/asm/io_apic.h |1 + arch/x86/kernel/acpi/boot.c| 13 +++--- arch/x86/kernel/apic/io_apic.c |

[Patch v7 14/18] x86, irq, ACPI: Introduce a rwsem to protect IOAPIC operations from hotplug

We are going to support ACPI based IOAPIC hotplug, so introduce a rwsem to protect IOAPIC data structures from IOAPIC hotplug. We choose to serialize in ACPI instead of in the IOAPIC core because: 1) currently we are only plan to support ACPI based IOAPIC hotplug 2) it's much more cleaner and

[Patch v7 18/18] x86, irq, ACPI: Implement ACPI driver to support IOAPIC hotplug

Enable support of IOAPIC hotplug by: 1) reintroducing ACPI based IOAPIC driver 2) enhance pci_root driver to hook hotplug events The ACPI IOAPIC driver is always enabled if all of ACPI, PCI and IOAPIC are enabled. Signed-off-by: Jiang Liu --- drivers/acpi/Kconfig|6 ++

Re: [PATCH] ACPI / GPIO: Driver GPIO mappings for ACPI GPIOs

On Sat, Oct 25, 2014 at 7:05 AM, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > Provide a way for device drivers using GPIOs described by ACPI > GpioIo resources in _CRS to tell the GPIO subsystem what names > (connection IDs) to associate with specific GPIO pins defined > in there. > >

[Patch v7 17/18] x86, irq: Introduce helper to check whether an IOAPIC has been registered

Introduce acpi_ioapic_registered() to check whether an IOAPIC has already been registered, it will be used when enabling IOAPIC hotplug. Signed-off-by: Jiang Liu --- arch/x86/include/asm/io_apic.h |1 + arch/x86/kernel/acpi/boot.c| 22 ++

[Patch v7 13/18] x86, irq: Refine mp_register_ioapic() to prepare for IOAPIC hotplug

Refine mp_register_ioapic() to prepare for IOAPIC hotplug by: 1) change return value from void to int. 2) check for gsi range conflicts 3) check for IOAPIC physical address conflicts 4) enhance the way to allocate IOAPIC index Signed-off-by: Jiang Liu --- arch/x86/include/asm/io_apic.h |4

[Patch v7 15/18] x86, irq, ACPI: Implement interface to support ACPI based IOAPIC hot-addition

Implement acpi_register_ioapic() and enhance mp_register_ioapic() to support ACPI based IOAPIC hot-addition. Signed-off-by: Jiang Liu --- arch/x86/kernel/acpi/boot.c| 31 +-- arch/x86/kernel/apic/io_apic.c | 22 +- 2 files changed, 50

[Patch v7 12/18] x86, irq: Keep balance of IOAPIC pin reference count

To keep balance of IOAPIC pin reference count, we need to protect pirq_enable_irq(), acpi_pci_irq_enable() and intel_mid_pci_irq_enable() from reentrance. There are two cases which will cause reentrance. The first case is caused by suspend/hibernation. If pcibios_disable_irq is called during

[Patch v7 11/18] x86, irq: Remove __init marker for functions will be used by IOAPIC hotplug

Remove __init marker for functions which will be used by IOAPIC hotplug at runtime. Signed-off-by: Jiang Liu --- arch/x86/include/asm/io_apic.h |4 ++-- arch/x86/kernel/apic/io_apic.c | 18 +- 2 files changed, 11 insertions(+), 11 deletions(-) diff --git

[Patch v7 07/18] ACPI: Add interfaces to parse IOAPIC ID for IOAPIC hotplug

From: Yinghai Lu We need to parse APIC ID for IOAPIC registration for IOAPIC hotplug. ACPI _MAT method and MADT table are used to figure out IOAPIC ID, just like parsing CPU APIC ID for CPU hotplug. Signed-off-by: Yinghai Lu Signed-off-by: Jiang Liu --- drivers/acpi/processor_core.c | 122

[Patch v7 09/18] x86, irq: Split out alloc_ioapic_save_registers()

From: Yinghai Lu Split out alloc_ioapic_save_registers() from early_irq_init(), so it could be used for ioapic hotplug later. Signed-off-by: Yinghai Lu Signed-off-by: Jiang Liu Cc: Joerg Roedel Cc: Konrad Rzeszutek Wilk Cc: Sebastian Andrzej Siewior --- arch/x86/kernel/apic/io_apic.c |

[Patch v7 10/18] x86, irq: Prefer assigned ID in APIC ID register for x86_64

From: Yinghai Lu Perfer the assigned ID in APIC ID register for x86_64 if it's still available. Signed-off-by: Yinghai Lu Cc: Joerg Roedel Cc: Konrad Rzeszutek Wilk Cc: Sebastian Andrzej Siewior Signed-off-by: Jiang Liu --- arch/x86/kernel/apic/io_apic.c | 35

[Patch v7 08/18] PCI: Remove PCI ioapic driver

To support IOAPIC hotplug on x86 and IA64 platforms, OS needs to figure out global interrupt source number(GSI) and IOAPIC enumeration ID through ACPI interfaces. So BIOS must implement an ACPI IOAPIC device with _GSB/_UID or _MAT method to support IOAPIC hotplug. OS also needs to figure out base

[Patch v7 05/18] ACPI: Correct return value of acpi_dev_resource_address_space()

Change acpi_dev_resource_address_space() to return failure if the acpi_resource structure can't be converted to an ACPI address64 structure, so caller could correctly detect failure. Signed-off-by: Jiang Liu --- drivers/acpi/resource.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[Patch v7 04/18] x86, PCI, ACPI: Kill private function resource_to_addr() in arch/x86/pci/acpi.c

Private function resource_to_addr() is used to parse ACPI resources for PCI host bridge. There are public interfaces available for that purpose, so replace resource_to_addr() with public interfaces. Reviewed-by: Bjorn Helgaas Signed-off-by: Jiang Liu --- arch/x86/pci/acpi.c | 144

[Patch v7 03/18] ACPI, irq, x86: Return IRQ instead of GSI in mp_register_gsi()

The GSI for ACPI SCI may be shared with other devices. For example, Function mp_register_gsi() should return IRQ number, so fix a regression by returning mp_map_gsi_to_irq(gsi, 0) instead of gsi. The regression was caused by commit 84245af7297ced9e8fe "x86, irq, ACPI: Change __acpi_register_gsi

[Patch v7 02/18] x86, intel-mid: Create IRQs for APB timers and RTC timers

Intel MID platforms has no legacy interrupts, so no IRQ descriptors preallocated. We need to call mp_map_gsi_to_irq() to create IRQ descriptors for APB timers and RTC timers, otherwise it may cause invalid memory access as: [0.116839] BUG: unable to handle kernel NULL pointer dereference at

[Patch v7 01/18] ACPI, irq: fix regression casued by 6b9fb7082409

When IOAPIC is disabled, acpi_gsi_to_irq() should return gsi directly instead of calling mp_map_gsi_to_irq() to translate gsi to IRQ by IOAPIC. It fixes https://bugzilla.kernel.org/show_bug.cgi?id=84381. Reported-by: Thomas Richter Signed-off-by: Jiang Liu Cc: rui.zh...@intel.com Cc: # 3.17

[Patch v7 00/18] Enable support of IOAPIC hotplug on x86 platforms

This patch set enhances IOAPIC core and ACPI drivers to support IOAPIC hotplug on x86 platforms. It's based on v3.18-rc2 at https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git You may pull it from https://github.com/jiangliu/linux.git ioapic/hotplug_v7 We have pick up several

[Patch v7 00/18] Enable support of IOAPIC hotplug on x86 platforms

This patch set enhances IOAPIC core and ACPI drivers to support IOAPIC hotplug on x86 platforms. It's based on v3.18-rc2 at https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git You may pull it from https://github.com/jiangliu/linux.git ioapic/hotplug_v7 We have pick up several

linux-next: Tree for Oct 27

Hi all, Changes since 20141023: New trees: thermal-soc, y2038 The bluetooth tree gained a build failure so I used the version from next-20141023. The sound-asoc tree lost its build failure. The pinctrl tree gained a build failure so I used the version from next-20141023. The akpm-current

[PATCH v2] timekeeping: Added a function to return tv_sec portion of ktime_get_real_ts64()

The following patch adds a function to return tv_sec portion of ktime_get_real_ts64() function in order to have a function that returns seconds as 64-bit integers instead of 32-bit integers to address the y2038 problem. The function is similar to get_seconds() function except that it includes

Re: [PATCH] gpio: msm-v1: Fix typo in function argument

On Fri, Oct 24, 2014 at 11:29 PM, Daniel Thompson wrote: > irq_set_irq_wake() treats its second argument as a boolean. It is much > easier to read code when constant booleans are either 0 or 1! > > This particular line of code distracted me somewhat when I was doing a bit of > work in a code

linux-next: build failure after merge of the akpm-current tree

Hi Andrew, After merging the akpm-current tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: mm/cma.c: In function 'cma_declare_contiguous': mm/cma.c:288:4: error: implicit declaration of function 'phys_to_virt' [-Werror=implicit-function-declaration]

[PATCH] CXL: Fix PSL error due to duplicate segment table entries

From: Ian Munsie In certain circumstances the PSL can send an interrupt for a segment miss that the kernel has already handled. This can happen if multiple translations for the same segment are queued in the PSL before the kernel has restarted the first translation. The CXL driver did not

nanosleep truncated on 64 bit Linux by 292 billion years

I noticed that nanosleep() on 64 bit, "only" supports 292 years, rather than the full potential 292 billion years with 64 bit time_t, due to: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/include/linux/time.h?id=refs/tags/v3.16#n87 Attached is a program from Paul Eggert

Re: [PATCH v2 09/15] net: dsa: Add support for switch EEPROM access

On 10/26/2014 07:41 PM, Andrew Lunn wrote: On Sun, Oct 26, 2014 at 09:52:39AM -0700, Guenter Roeck wrote: On some chips it is possible to access the switch eeprom. Add infrastructure support for it. Signed-off-by: Guenter Roeck --- v2: - Add support for configuring switch EEPROM size through

RE: [PATCH] cpufreq: qoriq: Make the driver usable on all QorIQ platforms

> -Original Message- > From: Viresh Kumar [mailto:viresh.ku...@linaro.org] > Sent: Tuesday, October 21, 2014 5:04 PM > To: Tang Yuantian-B29983 > Cc: Rafael J. Wysocki; Linux Kernel Mailing List; linux...@vger.kernel.org; > linuxppc-...@ozlabs.org > Subject: Re: [PATCH] cpufreq: qoriq:

linux-next: build failure after merge of the pinctrl tree

Hi Linus, After merging the pinctrl tree, today's linux-next build (arm multi_v7_defconfig) failed like this: drivers/pinctrl/samsung/pinctrl-exynos.c:1194:43: error: array type has incomplete element type static const struct samsung_pin_bank_data exynos7_pin_banks0[] __initconst = {

Re: [PATCH v9 05/12] x86, mpx: on-demand kernel allocation of bounds tables

On 10/24/2014 08:08 PM, Thomas Gleixner wrote: On Sun, 12 Oct 2014, Qiaowei Ren wrote: + /* +* Go poke the address of the new bounds table in to the +* bounds directory entry out in userspace memory. Note: +* we may race with another CPU instantiating the same

Re: [PATCH v2 02/16] pci: quirks: add quirk to avoid AMD NL to bind with xhci

On Fri, Oct 24, 2014 at 10:35:29AM -0600, Bjorn Helgaas wrote: > On Fri, Oct 17, 2014 at 04:53:27PM +0800, Huang Rui wrote: > > The dwc3 controller is the PCI-E device in AMD NL platform, but the class > > code > > of PCI header is 0x0c0330, the same with xHC. That's because it needs to > > meet

Re: [PATCH v9 11/12] x86, mpx: cleanup unused bound tables

On 10/24/2014 10:40 PM, Thomas Gleixner wrote: On Sun, 12 Oct 2014, Qiaowei Ren wrote: Since we are doing the freeing from munmap() (and other paths like it), we hold mmap_sem for write. If we fault, the page fault handler will attempt to acquire mmap_sem for read and we will deadlock. For now,

[PATCH] sched:skip loop non-idle cpus after find an idle cpu while find_idlest_cpu

Idle cpu is idler than non-idle cpu, so we needn't loop non-idle cpus after find an idle cpu. Signed-off-by:yaodongd...@huawei.com --- kernel/sched/fair.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c index 0b069bf..2445a23 100644

RE: ACPI regression: New Acer workarounds break Samsung NP900X

Hi, Thanks for letting me know. Though IMO the ACER behavior is not ACPI spec compliant, but following it still shouldn't break the others. Because it just requires EC firmware to always flag SCI_EVT when there is an event queued up. I couldn't see a special reason that a correct EC firmware

[PATCH] quirk for Lenovo Yoga 3: no rfkill switch

The Yoga 3 does not contain any physical rfkill switch. Therefore disable the rfkill switch identically to the Yoga 2 approach. Signed-off-by: Stephan Mueller --- drivers/platform/x86/ideapad-laptop.c | 7 +++ 1 file changed, 7 insertions(+) diff --git

[PATCH V2] Driver cpu: update online when cpu_up/down besides sysfs

The current per-cpu offline info won't be updated when we use any other method besides sysfs to call cpu_up/down. Thus the cpu/online can't reflect the real online status. This patch is going to fix the issue introduced by commit 0902a9044fa5b7a0456ea4daacec2c2b3189ba8c (Driver core: Use generic

Re: [LKP] [rcu] BUG: kernel_boot_hang mode:0x10d0

On Mon, 2014-10-27 at 10:04 +0800, kernel test robot wrote: > FYI, we noticed the below changes on > > commit eea203fea3484598280a07fe503e025e886297fb ("rcu: Use pr_alert/pr_cont > for printing logs") > > >

Re: [PATHC] net: napi_reuse_skb() should check pfmemalloc

From: Eric Dumazet Date: Thu, 23 Oct 2014 06:30:30 -0700 > From: Eric Dumazet > > Do not reuse skb if it was pfmemalloc tainted, otherwise > future frame might be dropped anyway. > > Signed-off-by: Eric Dumazet Applied, thanks Eric. -- To unsubscribe from this list: send the line

[PATCH v14 2/5] dt-bindings: document Rockchip thermal

This add the necessary binding documentation for the thermal found on Rockchip SoCs Signed-off-by: zhaoyifeng Signed-off-by: Caesar Wang --- .../bindings/thermal/rockchip-thermal.txt | 53 ++ 1 file changed, 53 insertions(+) create mode 100644

Re: [PATCH v2 09/15] net: dsa: Add support for switch EEPROM access

On Sun, Oct 26, 2014 at 09:52:39AM -0700, Guenter Roeck wrote: > On some chips it is possible to access the switch eeprom. > Add infrastructure support for it. > > Signed-off-by: Guenter Roeck > --- > v2: > - Add support for configuring switch EEPROM size through platform data > or devicetree

[PATCH v14 0/5] Rockchip soc thermal driver

This series patchs tested on rk3288 SDK board and pinky-v1,v2 board. I believe the driver can be used on the rk3288-evb board. Add this driver, The system can reset the entire chip when the thermal temperture over 120C, In case of rising over 125C when tha hardware shorting,The sodftware will

[PATCH v14 5/5] ARM: dts: enable Thermal on rk3288-evb board

when a thermal temperature over TSHUT.Default to via CRU reset the entire chip on rk3288-evb Board, TSHUT is low active on rk3288-evb board. Signed-off-by: Caesar Wang --- arch/arm/boot/dts/rk3288-evb.dtsi | 6 ++ 1 file changed, 6 insertions(+) diff --git

[PATCH v14 3/5] ARM: dts: add RK3288 Thermal data

This patch changes a dtsi file to contain the thermal data on RK3288 and later SoCs. This data will enable a thermal shutdown over 120C. Signed-off-by: Caesar Wang --- arch/arm/boot/dts/rk3288-thermal.dtsi | 65 +++ 1 file changed, 65 insertions(+) create mode

[PATCH v14 4/5] ARM: dts: add main Thermal info to rk3288

This patch is depend on rk3288-thermal.dtsi,or it will compile error. If for some reason we are unable to shut it down in orderly fashion (kernel is stuck holding a lock or similar), then hardware TSHUT will reset it. If the temperature over a period of time High,over 125C the resulting TSHUT

[PATCH v14 1/5] thermal: rockchip: add driver for thermal

Thermal is TS-ADC Controller module supports user-defined mode and automatic mode. User-defined mode refers,TSADC all the control signals entirely by software writing to register for direct control. Automaic mode refers to the module automatically poll TSADC output, and the results were

[PATCH] i386/audit: stop scribbling on the stack frame

git commit b4f0d3755c5e9cc86292d5fd78261903b4f23d4a was very very dumb. It was writing over %esp/pt_regs semi-randomly on i686 with the expected "system can't boot" results. As noted in: https://bugs.freedesktop.org/show_bug.cgi?id=85277 This patch stops fscking with pt_regs. Instead it sets

RE: [PATCH] drivers: base: update cpu offline info when do hotplug

> -Original Message- > From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: 2014年10月27日 10:27 > To: Neil Zhang > Cc: Dan Streetman; linux-kernel@vger.kernel.org > Subject: Re: [PATCH] drivers: base: update cpu offline info when do hotplug > > On Sun, Oct 26, 2014 at 07:17:14PM

Re: [PATCH] drivers: base: update cpu offline info when do hotplug

On Sun, Oct 26, 2014 at 07:17:14PM -0700, Neil Zhang wrote: > > > > -Original Message- > > From: Greg KH [mailto:gre...@linuxfoundation.org] > > Sent: 2014年10月27日 9:59 > > To: Neil Zhang > > Cc: Dan Streetman; linux-kernel@vger.kernel.org > > Subject: Re: [PATCH] drivers: base: update

[LKP] [ACPI / processor] f3ca4164529: -48.3% will-it-scale.per_process_ops

FYI, we noticed the below changes on commit f3ca4164529b875374c410193bbbac0ee960895f ("ACPI / processor: Rework processor throttling with work_on_cpu()") v3.14-rc4 f3ca4164529b875374c410193b testbox/testcase/testparams --

Re: [LKP] [futex] 76835b0ebf8: -12.1% will-it-scale.per_process_ops

On Mon, 2014-10-27 at 10:18 +0800, kernel test robot wrote: > FYI, we noticed the below changes on > > commit 76835b0ebf8a7fe85beb03c75121419a7dec52f0 ("futex: Ensure > get_futex_key_refs() always implies a barrier") fwiw I was also able to reproduce similar results, with the hashing costing

linux-next: build failure after merge of the bluetooth tree

Hi Gustavo, After merging the bluetooth tree, today's linux-next build (x86_64 allmodconfig) failed like this: net/bluetooth/smp.o: In function `test_smp': smp.c:(.init.text+0x0): multiple definition of `init_module' net/bluetooth/af_bluetooth.o:af_bluetooth.c:(.init.text+0x0): first defined

RE: [PATCH v9 10/12] x86, mpx: add prctl commands PR_MPX_ENABLE_MANAGEMENT, PR_MPX_DISABLE_MANAGEMENT

On 2014-10-24, Thomas Gleixner wrote: > On Sun, 12 Oct 2014, Qiaowei Ren wrote: >> +int mpx_enable_management(struct task_struct *tsk) { >> +struct mm_struct *mm = tsk->mm; >> +void __user *bd_base = MPX_INVALID_BOUNDS_DIR; > > What's the point of initializing bd_base here. I had to

[LKP] [futex] 76835b0ebf8: -12.1% will-it-scale.per_process_ops

FYI, we noticed the below changes on commit 76835b0ebf8a7fe85beb03c75121419a7dec52f0 ("futex: Ensure get_futex_key_refs() always implies a barrier") 0429fbc0bdc297d6 76835b0ebf8a7fe85beb03c751 testbox/testcase/testparams --

[LKP] [virtio_blk] kernel BUG at drivers/virtio/virtio.c:116!

FYI, we noticed the below changes on git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost-next commit 067da47bd4572e15532e303b6ced799540654589 ("virtio_blk: v1.0 support") +--+++ |

RE: [PATCH] drivers: base: update cpu offline info when do hotplug

> -Original Message- > From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: 2014年10月27日 9:59 > To: Neil Zhang > Cc: Dan Streetman; linux-kernel@vger.kernel.org > Subject: Re: [PATCH] drivers: base: update cpu offline info when do hotplug > > On Sun, Oct 26, 2014 at 06:43:11PM

[LKP] [AHCI] 18dcf433f3d: -3.3% fileio.requests_per_sec

FYI, we noticed the below changes on commit 18dcf433f3ded61eb140a55e7048ec2fef79e723 ("AHCI: Optimize single IRQ interrupt processing") 227dfb4dbf109596 18dcf433f3ded61eb140a55e70 testbox/testcase/testparams -- ---

[LKP] [mm] 3193913ce62: 4.7% will-it-scale.per_process_ops

FYI, we noticed the below changes on commit 3193913ce62c63056bc67a6ae378beaf494afa66 ("mm: page_alloc: default node-ordering on 64-bit NUMA, zone-ordering on 32-bit") 97ee4ba7cbd30f18 3193913ce62c63056bc67a6ae3 testbox/testcase/testparams --

[LKP] [sched] 8236d907ab3: 2% vm-scalability.throughput

FYI, we noticed the below changes on commit 8236d907ab3411ad452280faa8b26c1347327380 ("sched: Reduce contention in update_cfs_rq_blocked_load()") 5cd038f53ed9ec7a 8236d907ab3411ad452280faa8 testbox/testcase/testparams -- ---

[PATCH v2] ARM: kexec: Fix validating CPU hotplug support

v1 -> v2: -do some source format Due to commit:2103f6cba61a8b8bea3fc1b63661d830a2125e76, there is a hotplug checking in machine_kexec_prepare(), but it will lead a failure when loading the crash-kernel in some cases. Kexec utility can load the crash kernel by two ways: 1. kexec -l kernel-image

Re: [PATCH] i386/audit: stop scribbling on the stack frame

On 14/10/24, Andy Lutomirski wrote: > On Fri, Oct 24, 2014 at 1:19 PM, H. Peter Anvin wrote: > > On 10/23/2014 12:38 PM, Eric Paris wrote: > >>> After the call __audit_syscall_entry aren't they already polluted? > >>> Isn't that the reason we need to reload EAX? > >> > >> Well, I guess EAX is

[PATCH] zram: avoid NULL pointer access in concurrent situation

There is a rare NULL pointer bug in mem_used_total_show() and mem_used_max_store() in concurrent situation, like this: zram is not initialized, process A is a mem_used_total reader which runs periodically, while process B try to init zram. process A process

Re: [PATCH] netlink: don't copy over empty attribute data

From: Sasha Levin Date: Sun, 26 Oct 2014 19:32:42 -0400 > How so? GCC states clearly that you should *never* pass a NULL > pointer there: > > "The pointers passed to memmove (and similar functions in ) must > be non-null even when nbytes==0" > (https://gcc.gnu.org/gcc-4.9/porting_to.html). >

Re: [PATCH] i386/audit: stop scribbling on the stack frame

On 14/10/23, Eric Paris wrote: > On Thu, 2014-10-23 at 12:20 -0700, Andy Lutomirski wrote: > > On Thu, Oct 23, 2014 at 12:15 PM, Eric Paris wrote: > > > On Thu, 2014-10-23 at 11:39 -0700, Andy Lutomirski wrote: > > >> On 10/22/2014 09:04 PM, Eric Paris wrote: > > >> > git commit

Re: [PATCH] drivers: base: update cpu offline info when do hotplug

On Sun, Oct 26, 2014 at 06:43:11PM -0700, Neil Zhang wrote: > Greg, > > > > -Original Message- > > From: ddstr...@gmail.com [mailto:ddstr...@gmail.com] On Behalf Of Dan > > Streetman > > Sent: 2014年10月21日 1:03 > > To: Neil Zhang > > Cc: Greg KH; linux-kernel@vger.kernel.org > > Subject:

RE: [PATCH v9 09/12] x86, mpx: decode MPX instruction to get bound violation information

On 2014-10-24, Thomas Gleixner wrote: > On Sun, 12 Oct 2014, Qiaowei Ren wrote: > >> This patch sets bound violation fields of siginfo struct in #BR >> exception handler by decoding the user instruction and constructing >> the faulting pointer. >> >> This patch does't use the generic decoder,

RE: [PATCH] drivers: base: update cpu offline info when do hotplug

Greg, > -Original Message- > From: ddstr...@gmail.com [mailto:ddstr...@gmail.com] On Behalf Of Dan > Streetman > Sent: 2014年10月21日 1:03 > To: Neil Zhang > Cc: Greg KH; linux-kernel@vger.kernel.org > Subject: Re: [PATCH] drivers: base: update cpu offline info when do hotplug > > On Mon,

[PATCH 2/6] sched/dl: fix yield task artificial overrun

The yield semantic of deadline class is to reduce remaining runtime to zero, and then update_curr_dl() will stop it. However, comsumed bandwidth is reduced from the budget of yield task again even if it has already been set to zero which leads to artificial overrun. This patch fix it by reduce

[PATCH 6/6] sched/dl: don't check CONFIG_SMP in switched_from_dl

There are both UP and SMP version of pull_dl_task(), so don't need to check CONFIG_SMP in switched_from_dl(); Signed-off-by: Wanpeng Li --- kernel/sched/deadline.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c index 21de865..35d6dd5

  1   2   3   4   5   6   >