Re: [RFC PATCH 0/2] vfs: Use per-cpu list for SB's s_inodes list

On Tue, Feb 16, 2016 at 08:31:18PM -0500, Waiman Long wrote: > This patch is a replacement of my previous list batching patch - > https://lwn.net/Articles/674105/. Compared with the previous patch, > this one provides better performance and fairness. However, it also > requires a bit more changes

Re: [RFC PATCH 0/2] vfs: Use per-cpu list for SB's s_inodes list

On Tue, Feb 16, 2016 at 08:31:18PM -0500, Waiman Long wrote: > This patch is a replacement of my previous list batching patch - > https://lwn.net/Articles/674105/. Compared with the previous patch, > this one provides better performance and fairness. However, it also > requires a bit more changes

Re: [RFC 3/3] ARM: dts: Don't overheat the Odroid XU3-Lite on high load

On 18.02.2016 18:59, Marek Szyprowski wrote: > Hello, > > On 2016-02-18 05:42, Krzysztof Kozlowski wrote: >> On 18.02.2016 11:36, Viresh Kumar wrote: BTW, I found the issue. The order of trip points in DT: thermal_zone0/trip_point_0_hyst:5000 thermal_zone0/trip_point_0_temp:5

Re: [RFC 3/3] ARM: dts: Don't overheat the Odroid XU3-Lite on high load

On 18.02.2016 18:59, Marek Szyprowski wrote: > Hello, > > On 2016-02-18 05:42, Krzysztof Kozlowski wrote: >> On 18.02.2016 11:36, Viresh Kumar wrote: BTW, I found the issue. The order of trip points in DT: thermal_zone0/trip_point_0_hyst:5000 thermal_zone0/trip_point_0_temp:5

Re: [PATCH v2 5/6] rockchip: power-domain: Modify power domain driver for rk3399

Am Donnerstag, 18. Februar 2016, 11:08:05 schrieb Elaine Zhang: > This driver is modified to support RK3399 SoC. > > Signed-off-by: Elaine Zhang > --- > drivers/soc/rockchip/pm_domains.c | 55 > +++ 1 file changed, 55 insertions(+) >

Re: [PATCH v2 5/6] rockchip: power-domain: Modify power domain driver for rk3399

Am Donnerstag, 18. Februar 2016, 11:08:05 schrieb Elaine Zhang: > This driver is modified to support RK3399 SoC. > > Signed-off-by: Elaine Zhang > --- > drivers/soc/rockchip/pm_domains.c | 55 > +++ 1 file changed, 55 insertions(+) > > diff --git

Re: [PATCH] rose: correct integer overflow check

On Thu, Feb 18, 2016 at 04:03:16PM -0500, Insu Yun wrote: > > Because of the types on the right hand side of the comparison > the expressions are all promoted to unsigned. > > Did you look at the compiler's assembler output?  I did when > reviewing your patch. > > > I checked

Re: [PATCH] rose: correct integer overflow check

On Thu, Feb 18, 2016 at 04:03:16PM -0500, Insu Yun wrote: > > Because of the types on the right hand side of the comparison > the expressions are all promoted to unsigned. > > Did you look at the compiler's assembler output?  I did when > reviewing your patch. > > > I checked

Re: [PATCH 1/1] ser_gigaset: use container_of() instead of detour

Hi Greg, On do, 2016-02-18 at 15:46 -0800, Greg KH wrote: > > > This is not the correct way to submit patches for inclusion in the > stable kernel tree. Please read Documentation/stable_kernel_rules.txt > for how to do this properly. > > What in my submission triggers this formletter?

Re: [PATCH 1/1] ser_gigaset: use container_of() instead of detour

Hi Greg, On do, 2016-02-18 at 15:46 -0800, Greg KH wrote: > > > This is not the correct way to submit patches for inclusion in the > stable kernel tree. Please read Documentation/stable_kernel_rules.txt > for how to do this properly. > > What in my submission triggers this formletter?

Re: [PATCH v2 6/6] dt/bindings: rockchip: modify document of Rockchip power domains

Am Donnerstag, 18. Februar 2016, 11:08:19 schrieb Elaine Zhang: > Add binding documentation for the power domains > found on Rockchip RK3399 SoCs > > Signed-off-by: Elaine Zhang This patch should probably include the devicetree people Rob Herring

Re: [PATCH v2 6/6] dt/bindings: rockchip: modify document of Rockchip power domains

Am Donnerstag, 18. Februar 2016, 11:08:19 schrieb Elaine Zhang: > Add binding documentation for the power domains > found on Rockchip RK3399 SoCs > > Signed-off-by: Elaine Zhang This patch should probably include the devicetree people Rob Herring Pawel Moll Mark Rutland Ian Campbell Kumar

[PATCH 2/8] arm64: Add more test functions to insn.c

From: "David A. Long" Certain instructions are hard to execute correctly out-of-line (as in kprobes). Test functions are added to insn.[hc] to identify these. The instructions include any that use PC-relative addressing, change the PC, or change interrupt masking. For

[PATCH 2/8] arm64: Add more test functions to insn.c

From: "David A. Long" Certain instructions are hard to execute correctly out-of-line (as in kprobes). Test functions are added to insn.[hc] to identify these. The instructions include any that use PC-relative addressing, change the PC, or change interrupt masking. For efficiency and simplicity

[PATCH 0/8] arm64: Add kernel probes (kprobes) support

From: "David A. Long" This patchset is heavily based on Sandeepa Prabhu's ARM v8 kprobes patches, first seen in October 2013. This version attempts to address concerns raised by reviewers and also fixes problems discovered during testing. This patchset adds support for

[PATCH 0/8] arm64: Add kernel probes (kprobes) support

From: "David A. Long" This patchset is heavily based on Sandeepa Prabhu's ARM v8 kprobes patches, first seen in October 2013. This version attempts to address concerns raised by reviewers and also fixes problems discovered during testing. This patchset adds support for kernel probes(kprobes),

[PATCH 4/8] arm64: Kprobes with single stepping support

From: Sandeepa Prabhu Add support for basic kernel probes(kprobes) and jump probes (jprobes) for ARM64. Kprobes utilizes software breakpoint and single step debug exceptions supported on ARM v8. A software breakpoint is placed at the probe address to trap the

[PATCH 5/8] arm64: kprobes instruction simulation support

From: Sandeepa Prabhu Kprobes needs simulation of instructions that cannot be stepped from different memory location, e.g.: those instructions that uses PC-relative addressing. In simulation, the behaviour of the instruction is implemented using a copy of pt_regs.

[PATCH 4/8] arm64: Kprobes with single stepping support

From: Sandeepa Prabhu Add support for basic kernel probes(kprobes) and jump probes (jprobes) for ARM64. Kprobes utilizes software breakpoint and single step debug exceptions supported on ARM v8. A software breakpoint is placed at the probe address to trap the kernel execution into the kprobe

[PATCH 5/8] arm64: kprobes instruction simulation support

From: Sandeepa Prabhu Kprobes needs simulation of instructions that cannot be stepped from different memory location, e.g.: those instructions that uses PC-relative addressing. In simulation, the behaviour of the instruction is implemented using a copy of pt_regs. Following instruction

linux-next: manual merge of the crypto tree with the net tree

Hi Herbert, Today's linux-next merge of the crypto tree got a conflict in: net/ipv4/tcp.c between commit: 1eea84b74cd2 ("tcp: correctly crypto_alloc_hash return check") from the net tree and commit: cf80e0e47e0e ("tcp: Use ahash") from the crypto tree. I fixed it up (the latter

linux-next: manual merge of the crypto tree with the net tree

Hi Herbert, Today's linux-next merge of the crypto tree got a conflict in: net/ipv4/tcp.c between commit: 1eea84b74cd2 ("tcp: correctly crypto_alloc_hash return check") from the net tree and commit: cf80e0e47e0e ("tcp: Use ahash") from the crypto tree. I fixed it up (the latter

[PATCH 3/8] arm64: add copy_to/from_user to kprobes blacklist

From: "David A. Long" Currrently taking exceptions when accessing user data from a kprobe'd instruction doesn't work. Avoid this situation by blacklisting the relevant functions. Signed-off-by: David A. Long --- arch/arm64/lib/copy_from_user.S | 1 +

[PATCH 8/8] kprobes: Add arm64 case in kprobe example module

From: Sandeepa Prabhu Add info prints in sample kprobe handlers for ARM64 Signed-off-by: Sandeepa Prabhu --- samples/kprobes/kprobe_example.c | 8 1 file changed, 8 insertions(+) diff --git a/samples/kprobes/kprobe_example.c

Re: [PATCH v2 0/6] rockchip: power-domain: fix pm domain for support RK3399 SoC

Hi Elaine, your sending mechanism could use some improvements :-) I always get patches 1-4 correctly as replies to the cover-letter while patches 5+6 always come separately (missing in-reply-to?). I guess using git send-email might help with that. Also, Kevin Hilman was very involved in

[PATCH 3/8] arm64: add copy_to/from_user to kprobes blacklist

From: "David A. Long" Currrently taking exceptions when accessing user data from a kprobe'd instruction doesn't work. Avoid this situation by blacklisting the relevant functions. Signed-off-by: David A. Long --- arch/arm64/lib/copy_from_user.S | 1 + arch/arm64/lib/copy_to_user.S | 1 + 2

[PATCH 8/8] kprobes: Add arm64 case in kprobe example module

From: Sandeepa Prabhu Add info prints in sample kprobe handlers for ARM64 Signed-off-by: Sandeepa Prabhu --- samples/kprobes/kprobe_example.c | 8 1 file changed, 8 insertions(+) diff --git a/samples/kprobes/kprobe_example.c b/samples/kprobes/kprobe_example.c index 727eb21..0c72b8a

Re: [PATCH v2 0/6] rockchip: power-domain: fix pm domain for support RK3399 SoC

Hi Elaine, your sending mechanism could use some improvements :-) I always get patches 1-4 correctly as replies to the cover-letter while patches 5+6 always come separately (missing in-reply-to?). I guess using git send-email might help with that. Also, Kevin Hilman was very involved in

[PATCH 1/8] arm64: Add HAVE_REGS_AND_STACK_ACCESS_API feature

From: "David A. Long" Add HAVE_REGS_AND_STACK_ACCESS_API feature for arm64. Signed-off-by: David A. Long --- arch/arm64/Kconfig | 1 + arch/arm64/include/asm/ptrace.h | 31 +++ arch/arm64/kernel/ptrace.c | 117

[PATCH 6/8] arm64: Add trampoline code for kretprobes

From: William Cohen The trampoline code is used by kretprobes to capture a return from a probed function. This is done by saving the registers, calling the handler, and restoring the registers. The code then returns to the original saved caller return address. It is

[PATCH 7/8] arm64: Add kernel return probes support (kretprobes)

From: Sandeepa Prabhu The pre-handler of this special 'trampoline' kprobe executes the return probe handler functions and restores original return address in ELR_EL1. This way the saved pt_regs still hold the original register context to be carried back to the probed

[PATCH 1/8] arm64: Add HAVE_REGS_AND_STACK_ACCESS_API feature

From: "David A. Long" Add HAVE_REGS_AND_STACK_ACCESS_API feature for arm64. Signed-off-by: David A. Long --- arch/arm64/Kconfig | 1 + arch/arm64/include/asm/ptrace.h | 31 +++ arch/arm64/kernel/ptrace.c | 117 3 files

[PATCH 6/8] arm64: Add trampoline code for kretprobes

From: William Cohen The trampoline code is used by kretprobes to capture a return from a probed function. This is done by saving the registers, calling the handler, and restoring the registers. The code then returns to the original saved caller return address. It is necessary to do this

[PATCH 7/8] arm64: Add kernel return probes support (kretprobes)

From: Sandeepa Prabhu The pre-handler of this special 'trampoline' kprobe executes the return probe handler functions and restores original return address in ELR_EL1. This way the saved pt_regs still hold the original register context to be carried back to the probed kernel function.

RE: linux-next: build failure after merge of the net-next tree

> > After merging the net-next tree, today's linux-next build (powerpc > > ppc64_defconfig) failed like this: > > > > In file included from drivers/net/ethernet/broadcom/bnx2x/bnx2x.h:56:0, > > from drivers/net/ethernet/broadcom/bnx2x/bnx2x_dcb.c:30: > >

RE: linux-next: build failure after merge of the net-next tree

> > After merging the net-next tree, today's linux-next build (powerpc > > ppc64_defconfig) failed like this: > > > > In file included from drivers/net/ethernet/broadcom/bnx2x/bnx2x.h:56:0, > > from drivers/net/ethernet/broadcom/bnx2x/bnx2x_dcb.c:30: > >

Re: [PATCH v1] tty: serial: Use GFP_ATOMIC instead of GFP_KERNEL in serial8250_em485_init()

On Thu, Feb 18, 2016 at 11:29:07PM +0300, Matwey V. Kornilov wrote: > 2016-02-18 23:21 GMT+03:00 Andy Shevchenko : > > On Thu, Feb 18, 2016 at 8:47 PM, Matwey V. Kornilov > > wrote: > >> serial8250_em485_init() is supposed to be protected with > >>

Re: [PATCH v1] tty: serial: Use GFP_ATOMIC instead of GFP_KERNEL in serial8250_em485_init()

On Thu, Feb 18, 2016 at 11:29:07PM +0300, Matwey V. Kornilov wrote: > 2016-02-18 23:21 GMT+03:00 Andy Shevchenko : > > On Thu, Feb 18, 2016 at 8:47 PM, Matwey V. Kornilov > > wrote: > >> serial8250_em485_init() is supposed to be protected with > >> p->port.lock spinlock. > >> This may lead to

Re: [PATCH 1/1] ser_gigaset: use container_of() instead of detour

On Thu, Feb 18, 2016 at 09:29:08PM +0100, Paul Bolle wrote: > The purpose of gigaset_device_release() is to kfree() the struct > ser_cardstate that contains our struct device. This is done via a bit of > a detour. First we make our struct device's driver_data point to the > container of our struct

Re: [PATCH 1/1] ser_gigaset: use container_of() instead of detour

On Thu, Feb 18, 2016 at 09:29:08PM +0100, Paul Bolle wrote: > The purpose of gigaset_device_release() is to kfree() the struct > ser_cardstate that contains our struct device. This is done via a bit of > a detour. First we make our struct device's driver_data point to the > container of our struct

Re: [PATCH 2/2] pinctrl: mediatek: add input-enable and direction setting for eint resources

On Tue, Feb 16, 2016 at 8:16 PM, Biao Huang wrote: > To use pin as eint, user should make sure that: > 1. pin is set to right mode, this is done in .irq_request_resources > implementation already. > 2. direction of the pin is input, which should call GPIO API to set >

Re: [PATCH 2/2] pinctrl: mediatek: add input-enable and direction setting for eint resources

On Tue, Feb 16, 2016 at 8:16 PM, Biao Huang wrote: > To use pin as eint, user should make sure that: > 1. pin is set to right mode, this is done in .irq_request_resources > implementation already. > 2. direction of the pin is input, which should call GPIO API to set > pin to input gpio. > We add

Re: [PATCH 1/1] intel_pstate: Increase hold-off time before busyness is scaled

On Fri, Feb 19, 2016 at 12:29 AM, Pandruvada, Srinivas wrote: > On Thu, 2016-02-18 at 20:43 +0100, Rafael J. Wysocki wrote: >> Hi Mel, >> >> On Thu, Feb 18, 2016 at 12:11 PM, Mel Gorman >> wrote: >> >> [cut] >> >> > >> > Signed-off-by:

Re: [PATCH 1/1] intel_pstate: Increase hold-off time before busyness is scaled

On Fri, Feb 19, 2016 at 12:29 AM, Pandruvada, Srinivas wrote: > On Thu, 2016-02-18 at 20:43 +0100, Rafael J. Wysocki wrote: >> Hi Mel, >> >> On Thu, Feb 18, 2016 at 12:11 PM, Mel Gorman >> wrote: >> >> [cut] >> >> > >> > Signed-off-by: Mel Gorman >> > --- >> > drivers/cpufreq/intel_pstate.c |

[PATCH next] ARM: virt: fix build of hyp-stub

processor does not support `isb' in ARM mode Signed-off-by: Vincent Stehlé <vincent.ste...@laposte.net> Cc: Jean-Philippe Brucker <jean-philippe.bruc...@arm.com> Cc: Marc Zyngier <marc.zyng...@arm.com> Cc: Russell King <rmk+ker...@arm.linux.org.uk> --- Hi, This can be seen

[PATCH next] ARM: virt: fix build of hyp-stub

processor does not support `isb' in ARM mode Signed-off-by: Vincent Stehlé Cc: Jean-Philippe Brucker Cc: Marc Zyngier Cc: Russell King --- Hi, This can be seen with linux next-20160218 and arm e.g. allmodconfig. Best regards, V. arch/arm/kernel/Makefile | 2 ++ 1 file changed, 2 insertions

Re: [PATCH 1/1] intel_pstate: Increase hold-off time before busyness is scaled

On Thu, 2016-02-18 at 20:43 +0100, Rafael J. Wysocki wrote: > Hi Mel, > > On Thu, Feb 18, 2016 at 12:11 PM, Mel Gorman > wrote: > > [cut] > > > > > Signed-off-by: Mel Gorman > > --- > >  drivers/cpufreq/intel_pstate.c | 2 +- > >  1

Re: [PATCH 1/1] intel_pstate: Increase hold-off time before busyness is scaled

On Thu, 2016-02-18 at 20:43 +0100, Rafael J. Wysocki wrote: > Hi Mel, > > On Thu, Feb 18, 2016 at 12:11 PM, Mel Gorman > wrote: > > [cut] > > > > > Signed-off-by: Mel Gorman > > --- > >  drivers/cpufreq/intel_pstate.c | 2 +- > >  1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff

Re: [PATCH] pinctrl: mediatek: fix platform_no_drv_owner.cocci warnings

On Tue, Feb 16, 2016 at 11:06 PM, kbuild test robot wrote: > drivers/pinctrl/mediatek/pinctrl-mt2701.c:576:3-8: No need to set .owner > here. The core will do it. > > Remove .owner field if calls are used which set it automatically > > Generated by:

Re: [PATCH] pinctrl: mediatek: fix platform_no_drv_owner.cocci warnings

On Tue, Feb 16, 2016 at 11:06 PM, kbuild test robot wrote: > drivers/pinctrl/mediatek/pinctrl-mt2701.c:576:3-8: No need to set .owner > here. The core will do it. > > Remove .owner field if calls are used which set it automatically > > Generated by:

Re: [PATCH v2 5/5] gpio: allow setting ARCH_NR_GPIOS from Kconfig

On Tue, Feb 16, 2016 at 4:40 PM, Arnd Bergmann wrote: > The ARM version of asm/gpio.h basically just contains the same definitions > as the gpiolib version, with the exception of ARCH_NR_GPIOS. > > This adds the option for overriding the constant through Kconfig to > the

Re: [PATCH v2 5/5] gpio: allow setting ARCH_NR_GPIOS from Kconfig

On Tue, Feb 16, 2016 at 4:40 PM, Arnd Bergmann wrote: > The ARM version of asm/gpio.h basically just contains the same definitions > as the gpiolib version, with the exception of ARCH_NR_GPIOS. > > This adds the option for overriding the constant through Kconfig to > the architecture-independent

Re: [PATCH v2 4/5] gpio: ep93xx: remove private irq_to_gpio function

On Tue, Feb 16, 2016 at 4:40 PM, Arnd Bergmann wrote: > The ep93xx goes through its own back-and-forth dance every time > it wants to know the gpio number for an irq line, when it really > just hardcodes a fixed offset in ep93xx_gpio_to_irq(). > > This removes the pointless macro

Re: [PATCH v2 4/5] gpio: ep93xx: remove private irq_to_gpio function

On Tue, Feb 16, 2016 at 4:40 PM, Arnd Bergmann wrote: > The ep93xx goes through its own back-and-forth dance every time > it wants to know the gpio number for an irq line, when it really > just hardcodes a fixed offset in ep93xx_gpio_to_irq(). > > This removes the pointless macro and replaces

Re: [PATCH v2 3/5] gpio: ks8695: remove irq_to_gpio function

On Tue, Feb 16, 2016 at 4:40 PM, Arnd Bergmann wrote: > The ks8695 gpio driver has its own copy of the irq_to_gpio() > function. This is completely unused in the mainline kernel > after we converted all remaining users several years ago, > so we can remove the definition as well.

Re: [PATCH v2 3/5] gpio: ks8695: remove irq_to_gpio function

On Tue, Feb 16, 2016 at 4:40 PM, Arnd Bergmann wrote: > The ks8695 gpio driver has its own copy of the irq_to_gpio() > function. This is completely unused in the mainline kernel > after we converted all remaining users several years ago, > so we can remove the definition as well. > >

Re: [PATCH v2 2/5] gpio: remove broken irq_to_gpio() interface

On Tue, Feb 16, 2016 at 4:40 PM, Arnd Bergmann wrote: > gpiolib has removed the irq_to_gpio() API several years ago, > but the global header still provided a non-working stub. > > To prevent new users of this broken function from showing > up, let's remove the stubs as well. > >

Re: [PATCH v2 2/5] gpio: remove broken irq_to_gpio() interface

On Tue, Feb 16, 2016 at 4:40 PM, Arnd Bergmann wrote: > gpiolib has removed the irq_to_gpio() API several years ago, > but the global header still provided a non-working stub. > > To prevent new users of this broken function from showing > up, let's remove the stubs as well. > > Signed-off-by:

Re: [PATCH v2 1/5] MIPS: jz4740: remove broken irq_to_gpio() call

On Tue, Feb 16, 2016 at 5:06 PM, Ralf Baechle wrote: >> -#define IRQ_TO_BIT(irq) BIT(irq_to_gpio(irq) & 0x1f) >> +#define IRQ_TO_BIT(irq) BIT((irq - JZ4740_IRQ_GPIO(0)) & 0x1f) >> >> static void jz_gpio_check_trigger_both(struct jz_gpio_chip *chip, unsigned >> int irq) >>

Re: [PATCH v2 1/5] MIPS: jz4740: remove broken irq_to_gpio() call

On Tue, Feb 16, 2016 at 5:06 PM, Ralf Baechle wrote: >> -#define IRQ_TO_BIT(irq) BIT(irq_to_gpio(irq) & 0x1f) >> +#define IRQ_TO_BIT(irq) BIT((irq - JZ4740_IRQ_GPIO(0)) & 0x1f) >> >> static void jz_gpio_check_trigger_both(struct jz_gpio_chip *chip, unsigned >> int irq) >> { > > I've already

[PATCHv6 1/7] nvmem: Add flag to export NVMEM to root only

Legacy AT24, AT25 EEPROMs are exported in sys so that only root can read the contents. The EEPROMs may contain sensitive information. Add a flag so the provide can indicate that NVMEM should also restrict access to root only. Signed-off-by: Andrew Lunn --- drivers/nvmem/core.c

[PATCHv6 1/7] nvmem: Add flag to export NVMEM to root only

Legacy AT24, AT25 EEPROMs are exported in sys so that only root can read the contents. The EEPROMs may contain sensitive information. Add a flag so the provide can indicate that NVMEM should also restrict access to root only. Signed-off-by: Andrew Lunn --- drivers/nvmem/core.c | 57

[PATCHv6 6/7] eeprom: 93xx46: extend driver to plug into the NVMEM framework

Add a regmap for accessing the EEPROM, and then use that with the NVMEM framework. Enable backward compatibility in the NVMEM config structure, so that the 'eeprom' file in sys is provided by the framework. Signed-off-by: Andrew Lunn Acked-by: Srinivas Kandagatla

[PATCHv6 5/7] eeprom: at25: extend driver to plug into the NVMEM framework

Add a regmap for accessing the EEPROM, and then use that with the NVMEM framework. Enable backwards compatibility in the NVMEM config, so that the 'eeprom' file in sys is provided by the framework. Signed-off-by: Andrew Lunn Acked-by: Srinivas Kandagatla

[PATCHv6 0/7] Convert exiting EEPROM drivers to NVMEM

This patch set converts the old EEPROM drivers in driver/misc/eeprom to use the NVMEM framework. These drivers export there content in /sys as read only to root, since the EEPROM may contain sensitive information. So the first patch adds a flag so the NVMEM framework will create its file in /sys

[PATCHv6 4/7] eeprom: at25: Remove in kernel API for accessing the EEPROM

The setup() callback is not used by any in kernel code. Remove it. Any new code which requires access to the eeprom can use the NVMEM API. Signed-off-by: Andrew Lunn Acked-by: Srinivas Kandagatla --- drivers/misc/eeprom/at25.c | 26

[PATCHv6 2/7] nvmem: Add backwards compatibility support for older EEPROM drivers.

Older drivers made an 'eeprom' file available in the /sys device directory. Have the NVMEM core provide this to retain backwards compatibility. Signed-off-by: Andrew Lunn --- v4: Add lockdep support --- drivers/nvmem/core.c | 84

[PATCHv6 6/7] eeprom: 93xx46: extend driver to plug into the NVMEM framework

Add a regmap for accessing the EEPROM, and then use that with the NVMEM framework. Enable backward compatibility in the NVMEM config structure, so that the 'eeprom' file in sys is provided by the framework. Signed-off-by: Andrew Lunn Acked-by: Srinivas Kandagatla --- v5: Remove useless test.

[PATCHv6 5/7] eeprom: at25: extend driver to plug into the NVMEM framework

Add a regmap for accessing the EEPROM, and then use that with the NVMEM framework. Enable backwards compatibility in the NVMEM config, so that the 'eeprom' file in sys is provided by the framework. Signed-off-by: Andrew Lunn Acked-by: Srinivas Kandagatla --- drivers/misc/eeprom/Kconfig | 2 +

[PATCHv6 0/7] Convert exiting EEPROM drivers to NVMEM

This patch set converts the old EEPROM drivers in driver/misc/eeprom to use the NVMEM framework. These drivers export there content in /sys as read only to root, since the EEPROM may contain sensitive information. So the first patch adds a flag so the NVMEM framework will create its file in /sys

[PATCHv6 4/7] eeprom: at25: Remove in kernel API for accessing the EEPROM

The setup() callback is not used by any in kernel code. Remove it. Any new code which requires access to the eeprom can use the NVMEM API. Signed-off-by: Andrew Lunn Acked-by: Srinivas Kandagatla --- drivers/misc/eeprom/at25.c | 26 -- include/linux/spi/eeprom.h | 2 --

[PATCHv6 2/7] nvmem: Add backwards compatibility support for older EEPROM drivers.

Older drivers made an 'eeprom' file available in the /sys device directory. Have the NVMEM core provide this to retain backwards compatibility. Signed-off-by: Andrew Lunn --- v4: Add lockdep support --- drivers/nvmem/core.c | 84 ++

[PATCHv6 7/7] misc: at24: replace memory_accessor with nvmem_device_read

Now that the AT24 uses the NVMEM framework, replace the memory_accessor in the setup() callback with nvmem API calls. Signed-off-by: Andrew Lunn Acked-by: Srinivas Kandagatla --- arch/arm/mach-davinci/board-mityomapl138.c | 5 +++--

[PATCHv6 3/7] eeprom: at24: extend driver to plug into the NVMEM framework

Add a regmap for accessing the EEPROM, and then use that with the NVMEM framework. Set the NVMEM config structure to enable backward, so that the 'eeprom' file in sys is provided by the framework. Signed-off-by: Andrew Lunn Acked-by: Srinivas Kandagatla

[PATCHv6 7/7] misc: at24: replace memory_accessor with nvmem_device_read

Now that the AT24 uses the NVMEM framework, replace the memory_accessor in the setup() callback with nvmem API calls. Signed-off-by: Andrew Lunn Acked-by: Srinivas Kandagatla --- arch/arm/mach-davinci/board-mityomapl138.c | 5 +++-- arch/arm/mach-davinci/common.c | 4 ++--

[PATCHv6 3/7] eeprom: at24: extend driver to plug into the NVMEM framework

Add a regmap for accessing the EEPROM, and then use that with the NVMEM framework. Set the NVMEM config structure to enable backward, so that the 'eeprom' file in sys is provided by the framework. Signed-off-by: Andrew Lunn Acked-by: Srinivas Kandagatla Tested-by: Bartosz Golaszewski ---

Re: rcu_preempt self-detected stall on CPU from 4.5-rc3, since 3.17

- On Feb 18, 2016, at 6:51 AM, Ross Green rgker...@gmail.com wrote: > On Thu, Feb 18, 2016 at 10:19 AM, Paul E. McKenney > wrote: >> On Wed, Feb 17, 2016 at 12:28:29PM -0800, Paul E. McKenney wrote: >>> On Wed, Feb 17, 2016 at 08:45:54PM +0100, Peter Zijlstra

Re: rcu_preempt self-detected stall on CPU from 4.5-rc3, since 3.17

- On Feb 18, 2016, at 6:51 AM, Ross Green rgker...@gmail.com wrote: > On Thu, Feb 18, 2016 at 10:19 AM, Paul E. McKenney > wrote: >> On Wed, Feb 17, 2016 at 12:28:29PM -0800, Paul E. McKenney wrote: >>> On Wed, Feb 17, 2016 at 08:45:54PM +0100, Peter Zijlstra wrote: >>> > On Wed, Feb 17,

Re: [PATCH] hwmon: (ads1015) Handle negative conversion values correctly

Hi! Sorry for the noise, but... On 2016-02-18 14:07, Peter Rosin wrote: > From: Peter Rosin > > Make the divisor signed as DIV_ROUND_CLOSEST is undefined for negative > dividends when the divisor is unsigned. > > Signed-off-by: Peter Rosin ...I forgot to

Re: [PATCH] hwmon: (ads1015) Handle negative conversion values correctly

Hi! Sorry for the noise, but... On 2016-02-18 14:07, Peter Rosin wrote: > From: Peter Rosin > > Make the divisor signed as DIV_ROUND_CLOSEST is undefined for negative > dividends when the divisor is unsigned. > > Signed-off-by: Peter Rosin ...I forgot to add this to the commit message Cc:

Re: [PATCH] x86/perf/intel/cqm: Get rid of the silly for_each_cpu lookups

On Thu, 18 Feb 2016, Thomas Gleixner wrote: On Wed, 17 Feb 2016, Thomas Gleixner wrote: On Wed, 17 Feb 2016, Vikas Shivappa wrote: Please stop top posting, finally! But we have an extra static - static to avoid having it in the stack.. It's not about the cpu mask on the stack. The

Re: [PATCH] x86/perf/intel/cqm: Get rid of the silly for_each_cpu lookups

On Thu, 18 Feb 2016, Thomas Gleixner wrote: On Wed, 17 Feb 2016, Thomas Gleixner wrote: On Wed, 17 Feb 2016, Vikas Shivappa wrote: Please stop top posting, finally! But we have an extra static - static to avoid having it in the stack.. It's not about the cpu mask on the stack. The

linux-next: build failure after merge of the wireless-drivers-next tree

Hi Kalle, After merging the wireless-drivers-next tree, today's linux-next build failed the same way as the net-next tree did yesterday (suprise! :-)). I have used the version from next-20160218 for today. -- Cheers, Stephen Rothwell

linux-next: build failure after merge of the wireless-drivers-next tree

Hi Kalle, After merging the wireless-drivers-next tree, today's linux-next build failed the same way as the net-next tree did yesterday (suprise! :-)). I have used the version from next-20160218 for today. -- Cheers, Stephen Rothwell

Re: [RFC PATCH] proc: do not include shmem and driver pages in /proc/meminfo::Cached

On Thu, 18 Feb 2016, Johannes Weiner wrote: > Even before we added MemAvailable, users knew that page cache is > easily convertible to free memory on pressure, and estimated their > "available" memory by looking at the sum of MemFree, Cached, Buffers. > However, "Cached" is calculated using

Re: [RFC PATCH] proc: do not include shmem and driver pages in /proc/meminfo::Cached

On Thu, 18 Feb 2016, Johannes Weiner wrote: > Even before we added MemAvailable, users knew that page cache is > easily convertible to free memory on pressure, and estimated their > "available" memory by looking at the sum of MemFree, Cached, Buffers. > However, "Cached" is calculated using

Re: [PATCH 3/7] scsi: Drop runtime PM usage count after host is added

Hi Mika, On Thu, Feb 18, 2016 at 7:54 PM, Mika Westerberg wrote: > Runtime PM of the SCSI host is already handled by calls to > scsi_autopm_get_host() and scsi_autopm_put_host() from appropriate places > whenever the host needs to be powered on. This works fine

Re: [PATCH 3/7] scsi: Drop runtime PM usage count after host is added

Hi Mika, On Thu, Feb 18, 2016 at 7:54 PM, Mika Westerberg wrote: > Runtime PM of the SCSI host is already handled by calls to > scsi_autopm_get_host() and scsi_autopm_put_host() from appropriate places > whenever the host needs to be powered on. This works fine when there is > device connected

linux-next: manual merge of the net-next tree with the net tree

Hi all, Today's linux-next merge of the net-next tree got a conflict in: drivers/net/phy/marvell.c between commit: 79be1a1c9090 ("phy: marvell: Fix and unify reg-init behavior") from the net tree and commit: 930b37ee8d84 ("net: phy: Add SGMII support for Marvell

linux-next: manual merge of the net-next tree with the net tree

Hi all, Today's linux-next merge of the net-next tree got a conflict in: drivers/net/phy/marvell.c between commit: 79be1a1c9090 ("phy: marvell: Fix and unify reg-init behavior") from the net tree and commit: 930b37ee8d84 ("net: phy: Add SGMII support for Marvell

Re: tty: memory leak in tty_register_driver

Dmitry, On ma, 2016-02-15 at 11:42 +0100, Dmitry Vyukov wrote: > When I am running the following program in a parallel loop, kmemleak > starts reporting memory leaks of objects allocated in > tty_register_driver during boot. Because these tty drivers are built in? > These leaks start popping

Re: tty: memory leak in tty_register_driver

Dmitry, On ma, 2016-02-15 at 11:42 +0100, Dmitry Vyukov wrote: > When I am running the following program in a parallel loop, kmemleak > starts reporting memory leaks of objects allocated in > tty_register_driver during boot. Because these tty drivers are built in? > These leaks start popping

Re: [RFC][PATCH 00/10] Add trace event support to eBPF

On 02/18/2016 10:27 PM, Tom Zanussi wrote: On Tue, 2016-02-16 at 20:51 -0800, Alexei Starovoitov wrote: On Tue, Feb 16, 2016 at 04:35:27PM -0600, Tom Zanussi wrote: On Sun, 2016-02-14 at 01:02 +0100, Alexei Starovoitov wrote: [...] Take a look at all the tools written on top of it:

Re: [RFC][PATCH 00/10] Add trace event support to eBPF

On 02/18/2016 10:27 PM, Tom Zanussi wrote: On Tue, 2016-02-16 at 20:51 -0800, Alexei Starovoitov wrote: On Tue, Feb 16, 2016 at 04:35:27PM -0600, Tom Zanussi wrote: On Sun, 2016-02-14 at 01:02 +0100, Alexei Starovoitov wrote: [...] Take a look at all the tools written on top of it:

Re: [PATCH] bugfix of access a invalid addr

On Wed, Feb 17, 2016 at 3:02 AM, wrote: > From: chenjie > > when we run fs_fsbase_t, some testcase like > write05 failed > > write05 0 TINFO : Enter Block 1: test with bad fd > write05 1 TPASS : received EBADF as expected. > write05 0

Re: [PATCH] bugfix of access a invalid addr

On Wed, Feb 17, 2016 at 3:02 AM, wrote: > From: chenjie > > when we run fs_fsbase_t, some testcase like > write05 failed > > write05 0 TINFO : Enter Block 1: test with bad fd > write05 1 TPASS : received EBADF as expected. > write05 0 TINFO : Exit Block 1 > write05 0

Re: [RFC5 PATCH v6 00/21] ILP32 for ARM64

On Sat, Jan 30, 2016 at 12:15:45PM +0800, Zhangjian (Bamvor) wrote: > Hi, Yury > > On 1:09 2016/1/30, Yury Norov wrote: > >On Fri, Jan 29, 2016 at 05:59:33PM +0800, Zhangjian (Bamvor) wrote: > >>Hi, > >> > >>On 1:22 2016/1/15, Yury Norov wrote: > >>>This is still RFC because we have no glibc yet,

Re: [RFC5 PATCH v6 00/21] ILP32 for ARM64

On Sat, Jan 30, 2016 at 12:15:45PM +0800, Zhangjian (Bamvor) wrote: > Hi, Yury > > On 1:09 2016/1/30, Yury Norov wrote: > >On Fri, Jan 29, 2016 at 05:59:33PM +0800, Zhangjian (Bamvor) wrote: > >>Hi, > >> > >>On 1:22 2016/1/15, Yury Norov wrote: > >>>This is still RFC because we have no glibc yet,

Re: [PATCH v3 2/5] ACPI: parse SPCR and enable matching console

On 02/15/2016 10:05 AM, Aleksey Makarov wrote: > 'ARM Server Base Boot Requiremets' [1] mentions SPCR (Serial Port > Console Redirection Table) [2] as a mandatory ACPI table that > specifies the configuration of serial console. > > Parse this table and check if any registered console match the >

Re: [PATCH v3 2/5] ACPI: parse SPCR and enable matching console

On 02/15/2016 10:05 AM, Aleksey Makarov wrote: > 'ARM Server Base Boot Requiremets' [1] mentions SPCR (Serial Port > Console Redirection Table) [2] as a mandatory ACPI table that > specifies the configuration of serial console. > > Parse this table and check if any registered console match the >

<    1   2   3   4   5   6   7   8   9   10   >