[PATCH 47/61] gpio: timberdale Use devm_gpiochip_add_data() for gpio registration

Use devm_gpiochip_add_data() for GPIO registration. Signed-off-by: Laxman Dewangan --- drivers/gpio/gpio-timberdale.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/drivers/gpio/gpio-timberdale.c b/drivers/gpio/gpio-timberdale.c index a6de10c..f0164ec 100644 --- a/drivers

[PATCH 58/61] gpio: wm8350: Use devm_gpiochip_add_data() for gpio registration

Use devm_gpiochip_add_data() for GPIO registration and remove the need of driver callback .remove. Signed-off-by: Laxman Dewangan Cc: patc...@opensource.wolfsonmicro.com --- drivers/gpio/gpio-wm8350.c | 12 ++-- 1 file changed, 2 insertions(+), 10 deletions(-) diff --git a/drivers/gpio/

[PATCH 55/61] gpio: viperboard: Use devm_gpiochip_add_data() for gpio registration

Use devm_gpiochip_add_data() for GPIO registration and remove the need of driver callback .remove. Signed-off-by: Laxman Dewangan --- drivers/gpio/gpio-viperboard.c | 24 1 file changed, 4 insertions(+), 20 deletions(-) diff --git a/drivers/gpio/gpio-viperboard.c b/driv

[PATCH 54/61] gpio: ucb1400: Use devm_gpiochip_add_data() for gpio registration

Use devm_gpiochip_add_data() for GPIO registration. Signed-off-by: Laxman Dewangan --- drivers/gpio/gpio-ucb1400.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/gpio/gpio-ucb1400.c b/drivers/gpio/gpio-ucb1400.c index 2c5cd46..5dbe31b 100644 --- a/drivers/gpio/gpio

[PATCH 56/61] gpio: vx855: Use devm_gpiochip_add_data() for gpio registration

Use devm_gpiochip_add_data() for GPIO registration and remove the need of driver callback .remove. Signed-off-by: Laxman Dewangan --- drivers/gpio/gpio-vx855.c | 12 +--- 1 file changed, 1 insertion(+), 11 deletions(-) diff --git a/drivers/gpio/gpio-vx855.c b/drivers/gpio/gpio-vx855.c i

[PATCH 57/61] gpio: wm8350: Use devm_gpiochip_add_data() for gpio registration

Use devm_gpiochip_add_data() for GPIO registration and remove the need of driver callback .remove. Signed-off-by: Laxman Dewangan Cc: patc...@opensource.wolfsonmicro.com --- drivers/gpio/gpio-wm831x.c | 12 ++-- 1 file changed, 2 insertions(+), 10 deletions(-) diff --git a/drivers/gpio/

[PATCH 53/61] gpio: twl6040: Use devm_gpiochip_add_data() for gpio registration

Use devm_gpiochip_add_data() for GPIO registration and remove the need of driver callback .remove. Signed-off-by: Laxman Dewangan --- drivers/gpio/gpio-twl6040.c | 9 + 1 file changed, 1 insertion(+), 8 deletions(-) diff --git a/drivers/gpio/gpio-twl6040.c b/drivers/gpio/gpio-twl6040.c

[PATCH 00/61] gpio: Add and use devm_gpiochip_add_data()

Add resource management APIs for gpiochip_add_data() and gpiochip_remove() and use these APIs from different HW drivers. This is based on discussion on patch to use the new APIs. gpio: Add devm_ apis for gpio_chip_add and remove Laxman Dewangan (61): gpio: Add devm_ apis for gpiochip_a

[PATCH 52/61] gpio: ts5500: Use devm_gpiochip_add_data() for gpio registration

Use devm_gpiochip_add_data() for GPIO registration and clean the error path. Signed-off-by: Laxman Dewangan --- drivers/gpio/gpio-ts5500.c | 9 +++-- 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/drivers/gpio/gpio-ts5500.c b/drivers/gpio/gpio-ts5500.c index 5f94508..6cfeba0 1

[PATCH 05/61] gpio: adnp: Use devm_gpiochip_add_data() for gpio registration

Use devm_gpiochip_add_data() for GPIO registration and remove the call for gpiochip_remove() from error path. Also remove the need of driver callback .remove. Signed-off-by: Laxman Dewangan Cc: Alexandre Courbot --- drivers/gpio/gpio-adnp.c | 11 +-- 1 file changed, 1 insertion(+), 10

[PATCH 01/61] gpio: Add devm_ apis for gpiochip_add_data and gpiochip_remove

Add device managed APIs devm_gpiochip_add_data() and devm_gpiochip_remove() for the APIs gpiochip_add_data() and gpiochip_remove(). This helps in reducing code in error path and sometimes removal of .remove callback for driver unbind. Signed-off-by: Laxman Dewangan --- drivers/gpio/gpiolib.c

[PATCH 04/61] gpio: 74xx-mmio: Use devm_gpiochip_add_data() for gpio registration

Use devm_gpiochip_add_data() for GPIO registration and remove the call for gpiochip_remove() from error path. Also remove the need of driver callback .remove. Signed-off-by: Laxman Dewangan Cc: Alexander Shiyan --- drivers/gpio/gpio-74xx-mmio.c | 11 +-- 1 file changed, 1 insertion(+),

[PATCH 09/61] gpio: arizona: Use devm_gpiochip_add_data() for gpio registration

Use devm_gpiochip_add_data() for GPIO registration and remove the need of driver callback .remove. Signed-off-by: Laxman Dewangan Cc: patc...@opensource.wolfsonmicro.com --- drivers/gpio/gpio-arizona.c | 12 ++-- 1 file changed, 2 insertions(+), 10 deletions(-) diff --git a/drivers/gpio

[PATCH 08/61] gpio: amdpt: Use devm_gpiochip_add_data() for gpio registration

Use devm_gpiochip_add_data() for GPIO registration and remove the need of driver callback .remove. Signed-off-by: Laxman Dewangan --- drivers/gpio/gpio-amdpt.c | 12 +--- 1 file changed, 1 insertion(+), 11 deletions(-) diff --git a/drivers/gpio/gpio-amdpt.c b/drivers/gpio/gpio-amdpt.c i

[PATCH 12/61] gpio: clps711x: Use devm_gpiochip_add_data() for gpio registration

Use devm_gpiochip_add_data() for GPIO registration and remove the need of driver callback .remove. Signed-off-by: Laxman Dewangan --- drivers/gpio/gpio-clps711x.c | 11 +-- 1 file changed, 1 insertion(+), 10 deletions(-) diff --git a/drivers/gpio/gpio-clps711x.c b/drivers/gpio/gpio-clps

[PATCH 61/61] gpio: xgene: Use devm_gpiochip_add_data() for gpio registration

Use devm_gpiochip_add_data() for GPIO registration and remove the need of driver callback .remove. Signed-off-by: Laxman Dewangan --- drivers/gpio/gpio-xgene.c | 11 +-- 1 file changed, 1 insertion(+), 10 deletions(-) diff --git a/drivers/gpio/gpio-xgene.c b/drivers/gpio/gpio-xgene.c in

[PATCH 60/61] gpio: xgene-sb: Use devm_gpiochip_add_data() for gpio registration

Use devm_gpiochip_add_data() for GPIO registration. Signed-off-by: Laxman Dewangan --- drivers/gpio/gpio-xgene-sb.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/gpio/gpio-xgene-sb.c b/drivers/gpio/gpio-xgene-sb.c index 282004d..e665770 100644 --- a/drivers/gpio/g

[PATCH 59/61] gpio: wm8994: Use devm_gpiochip_add_data() for gpio registration

Use devm_gpiochip_add_data() for GPIO registration and remove the need of driver callback .remove. Signed-off-by: Laxman Dewangan Cc: patc...@opensource.wolfsonmicro.com --- drivers/gpio/gpio-wm8994.c | 17 +++-- 1 file changed, 3 insertions(+), 14 deletions(-) diff --git a/drivers/

[PATCH 51/61] gpio: ts4800: Use devm_gpiochip_add_data() for gpio registration

Use devm_gpiochip_add_data() for GPIO registration and remove the need of driver callback .remove. Signed-off-by: Laxman Dewangan --- drivers/gpio/gpio-ts4800.c | 12 +--- 1 file changed, 1 insertion(+), 11 deletions(-) diff --git a/drivers/gpio/gpio-ts4800.c b/drivers/gpio/gpio-ts4800.

[PATCH 50/61] gpio: tps65912: Use devm_gpiochip_add_data() for gpio registration

Use devm_gpiochip_add_data() for GPIO registration and remove the need of driver callback .remove. Signed-off-by: Laxman Dewangan --- drivers/gpio/gpio-tps65912.c | 12 ++-- 1 file changed, 2 insertions(+), 10 deletions(-) diff --git a/drivers/gpio/gpio-tps65912.c b/drivers/gpio/gpio-tp

[PATCH 48/61] gpio: tps6586x: Use devm_gpiochip_add_data() for gpio registration

Use devm_gpiochip_add_data() for GPIO registration and remove the need of driver callback .remove. Signed-off-by: Laxman Dewangan --- drivers/gpio/gpio-tps6586x.c | 12 ++-- 1 file changed, 2 insertions(+), 10 deletions(-) diff --git a/drivers/gpio/gpio-tps6586x.c b/drivers/gpio/gpio-tp

[PATCH 46/61] gpio: tegra: Use devm_gpiochip_add_data() for gpio registration

Use devm_gpiochip_add_data() for GPIO registration. Signed-off-by: Laxman Dewangan Cc: Stephen Warren Cc: Thierry Reding --- drivers/gpio/gpio-tegra.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpio/gpio-tegra.c b/drivers/gpio/gpio-tegra.c index 9a1a7e2..790bb1

[PATCH 45/61] gpio: tc3589x: Use devm_gpiochip_add_data() for gpio registration

Use devm_gpiochip_add_data() for GPIO registration and remove the need of driver callback .remove. Signed-off-by: Laxman Dewangan --- drivers/gpio/gpio-tc3589x.c | 13 ++--- 1 file changed, 2 insertions(+), 11 deletions(-) diff --git a/drivers/gpio/gpio-tc3589x.c b/drivers/gpio/gpio-tc3

[PATCH 38/61] gpio: sch: Use devm_gpiochip_add_data() for gpio registration

Use devm_gpiochip_add_data() for GPIO registration and remove the need of driver callback .remove. Signed-off-by: Laxman Dewangan --- drivers/gpio/gpio-sch.c | 11 +-- 1 file changed, 1 insertion(+), 10 deletions(-) diff --git a/drivers/gpio/gpio-sch.c b/drivers/gpio/gpio-sch.c index 53

[PATCH 11/61] gpio: bcm-kona: Use devm_gpiochip_add_data() for gpio registration

Use devm_gpiochip_add_data() for GPIO registration. Signed-off-by: Laxman Dewangan Cc: Ray Jui --- drivers/gpio/gpio-bcm-kona.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpio/gpio-bcm-kona.c b/drivers/gpio/gpio-bcm-kona.c index b6c5abe..2fd38d5 100644 --- a/dri

[PATCH 36/61] gpio: rc5t583: Use devm_gpiochip_add_data() for gpio registration

Use devm_gpiochip_add_data() for GPIO registration and remove the need of driver callback .remove. Signed-off-by: Laxman Dewangan --- drivers/gpio/gpio-rc5t583.c | 12 ++-- 1 file changed, 2 insertions(+), 10 deletions(-) diff --git a/drivers/gpio/gpio-rc5t583.c b/drivers/gpio/gpio-rc5t

Re: [PATCH v10 1/3] cpufreq: Add mechanism for registering utilization update callbacks

On 22 February 2016 at 11:52, Peter Zijlstra wrote: > On Fri, Feb 19, 2016 at 09:28:23AM -0800, Steve Muckle wrote: >> On 02/19/2016 08:42 AM, Srinivas Pandruvada wrote: >> > We did experiments using util/max in intel_pstate. For some benchmarks >> > there were regression of 4 to 5%, for some benc

Re: [PATCH 01/61] gpio: Add devm_ apis for gpiochip_add_data and gpiochip_remove

> +/** > + * devm_gpiochip_add_data() - Resource manager piochip_add_data() ^ missing g. > + * @dev: the device pointer on which irq_chip belongs to. > + * @chip: the chip to register, with chip->base initialized > + * Context: potentially before

[PATCH 26/61] gpio: lpc32xx: Use devm_gpiochip_add_data() for gpio registration

Use devm_gpiochip_add_data() for GPIO registration. Signed-off-by: Laxman Dewangan --- drivers/gpio/gpio-lpc32xx.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpio/gpio-lpc32xx.c b/drivers/gpio/gpio-lpc32xx.c index 4cecf4c..d39014d 100644 --- a/drivers/gpio/gpio-l

Re: [PATCH v3 1/5] ACPI: change __init to __ref for early_acpi_os_unmap_memory()

On 02/19/2016 06:25 PM, Peter Hurley wrote: > On 02/19/2016 02:42 AM, Aleksey Makarov wrote: >> Hi Peter, >> >> Thank you for review. >> >> On 02/19/2016 01:03 AM, Peter Hurley wrote: >>> On 02/17/2016 07:36 PM, Zheng, Lv wrote: Hi, > From: Aleksey Makarov [mailto:aleksey.maka...@lina

[PATCH 23/61] gpio: janz-ttl: Use devm_gpiochip_add_data() for gpio registration

Use devm_gpiochip_add_data() for GPIO registration and remove the need of driver callback .remove. Signed-off-by: Laxman Dewangan --- drivers/gpio/gpio-janz-ttl.c | 12 +--- 1 file changed, 1 insertion(+), 11 deletions(-) diff --git a/drivers/gpio/gpio-janz-ttl.c b/drivers/gpio/gpio-jan

Re: [Xen-devel] [PATCH 8/9] x86/rtc: replace paravirt_enabled() check with subarch check

On 02/22/2016 05:27 AM, Borislav Petkov wrote: On Mon, Feb 22, 2016 at 07:07:56AM +0100, Luis R. Rodriguez wrote: diff --git a/arch/x86/include/asm/x86_init.h b/arch/x86/include/asm/x86_init.h index 1ae89a2721d6..fe0d579b63e3 100644 --- a/arch/x86/include/asm/x86_init.h +++ b/arch/x86/include/as

[PATCH 19/61] gpio: f7188x: Use devm_gpiochip_add_data() for gpio registration

Use devm_gpiochip_add_data() for GPIO registration and remove the need of driver callback .remove. Signed-off-by: Laxman Dewangan --- drivers/gpio/gpio-f7188x.c | 26 ++ 1 file changed, 2 insertions(+), 24 deletions(-) diff --git a/drivers/gpio/gpio-f7188x.c b/drivers/gp

Re: [PATCH v10 1/3] cpufreq: Add mechanism for registering utilization update callbacks

Hi Peter, On 22/02/16 11:52, Peter Zijlstra wrote: > On Fri, Feb 19, 2016 at 09:28:23AM -0800, Steve Muckle wrote: > > On 02/19/2016 08:42 AM, Srinivas Pandruvada wrote: > > > We did experiments using util/max in intel_pstate. For some benchmarks > > > there were regression of 4 to 5%, for some be

Re: [PATCH 0/6] Support for systems without AArch32 state

On Mon, Feb 22, 2016 at 02:03:12PM +, Suzuki K. Poulose wrote: > On 28/01/16 11:32, Suzuki K Poulose wrote: > >This series add checks to make sure that the AArch32 state is > >supported before we process the 32bit ID registers. Also > >checks the same for COMPAT binary execution. > > Yuri, >

Re: [f2fs-dev] [PATCH 5/5] f2fs crypto: fix incorrect positioning for GCing encrypted data page

On 2016/2/22 18:38, Chao Yu wrote: > For now, flow of GCing an encrypted data page will be: > 1) try to grab meta page in meta inode's mapping with index of old block > address of that data page > 2) load data of ciphertext into meta page > 3) allocate new block address > 4) write the meta page int

[PATCH 10/61] gpio: ath79: Use devm_gpiochip_add_data() for gpio registration

Use devm_gpiochip_add_data() for GPIO registration. Signed-off-by: Laxman Dewangan Cc: Alban Bedel --- drivers/gpio/gpio-ath79.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpio/gpio-ath79.c b/drivers/gpio/gpio-ath79.c index d13dd13..a6aad59 100644 --- a/drivers/

[PATCH 07/61] gpio: adp5588: Use devm_gpiochip_add_data() for gpio registration

Use devm_gpiochip_add_data() for GPIO registration and remove the call for gpiochip_remove() from remove callback. Signed-off-by: Laxman Dewangan Cc: Michael Hennerich --- drivers/gpio/gpio-adp5588.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/drivers/gpio/gpio-adp558

[PATCH] ARM: dts: omap3-n900: Allow gpio keys to be disabled

Add linux,can-disable; to all gpios exported from gpio-keys driver, so userspace can disable them Signed-off-by: Ivaylo Dimitrov --- arch/arm/boot/dts/omap3-n900.dts | 6 ++ 1 file changed, 6 insertions(+) diff --git a/arch/arm/boot/dts/omap3-n900.dts b/arch/arm/boot/dts/omap3-n900.dts inde

Re: [PATCH v3 1/5] ACPI: change __init to __ref for early_acpi_os_unmap_memory()

On 02/19/2016 08:20 PM, Christopher Covington wrote: > > > On February 19, 2016 10:25:50 AM EST, Peter Hurley > wrote: >> On 02/19/2016 02:42 AM, Aleksey Makarov wrote: >>> Hi Peter, >>> >>> Thank you for review. >>> >>> On 02/19/2016 01:03 AM, Peter Hurley wrote: On 02/17/2016 07:36 PM,

Re: [PATCH 00/61] gpio: Add and use devm_gpiochip_add_data()

On Mon, Feb 22, 2016 at 3:07 PM, Laxman Dewangan wrote: > Add resource management APIs for gpiochip_add_data() and > gpiochip_remove() and use these APIs from different HW drivers. > > This is based on discussion on patch to use the new APIs. > gpio: Add devm_ apis for gpio_chip_add and r

[PATCH 41/61] gpio: stp-xway: Use devm_gpiochip_add_data() for gpio registration

Use devm_gpiochip_add_data() for GPIO registration. Signed-off-by: Laxman Dewangan --- drivers/gpio/gpio-stp-xway.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpio/gpio-stp-xway.c b/drivers/gpio/gpio-stp-xway.c index d11dd48..19e654f 100644 --- a/drivers/gpio/gpi

[PATCH 13/61] gpio: crystalcove: Use devm_gpiochip_add_data() for gpio registration

Use devm_gpiochip_add_data() for GPIO registration and remove the call of gpiochip_remove() from error path. Signed-off-by: Laxman Dewangan --- drivers/gpio/gpio-crystalcove.c | 9 ++--- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/drivers/gpio/gpio-crystalcove.c b/drivers/g

Re: richacl(7) man page review comments

Hi Michael, On Sun, Feb 21, 2016 at 10:40 PM, Michael Kerrisk (man-pages) wrote: > I've once more pulled from the latest git; here's some more comments. thanks again. I've updated the repo with your changes. >> .\" >> .\" RichACL Manual Pages >> .\" >> .\" Copyright (C) 2015,2016 Red Hat, Inc.

Re: [PATCH V3 1/2] irq: Track the interrupt timings

Hi Daniel, On 02/16/2016 09:13 PM, Daniel Lezcano wrote: > diff --git a/kernel/irq/irqdesc.c b/kernel/irq/irqdesc.c > index 0ccd028..577686b 100644 > --- a/kernel/irq/irqdesc.c > +++ b/kernel/irq/irqdesc.c > @@ -174,6 +174,9 @@ static struct irq_desc *alloc_desc(int irq, int node, > struct module

Re: [PATCH v6 02/12] arm-cci: Group writes to counter

On Mon, Jan 25, 2016 at 11:21:07AM +, Suzuki K. Poulose wrote: > Add a helper to group the writes to PMU counter, this will be > used to delay setting the event period to pmu::pmu_enable() > > Cc: Mark Rutland > Cc: Punit Agrawal > Signed-off-by: Suzuki K. Poulose > --- > Changes since V5:

[ANNOUNCE] Kselftest Framework mainling list - linux-kselft...@vger.kernel.org

Announcing new mailing list for Kselftest Framework. MAINTAINERS file has been updated in 4.5-rc5 thanks, -- Shuah -- Shuah Khan Sr. Linux Kernel Developer Open Source Innovation Group Samsung Research America (Silicon Valley) shua...@osg.samsung.com | (970) 217-8978

Re: [GIT PULL] remaining tpmdd fixes for Linux 4.5

On Mon, Feb 22, 2016 at 12:56:53PM +1100, James Morris wrote: > On Sat, 20 Feb 2016, Jarkko Sakkinen wrote: > > > Hi James, > > > > I'm sorry for the late pull request for 4.5. The reason for this was > > the latency in my previous one. I picked with care the absolutely > > critical fixes so that

[PATCH 2/2] device property: fix for a case of use-after-free

In device_remove_property_set(), if the primary fwnode is of type "pset", it has to be set pointing to NULL before calling set_secondary_fwnode(). Otherwise set_secondary_fwnode() will attempt to set the fwnode->secondary member after the fwnode has been freed. Reported-by: John Youn Signed-off-b

[PATCH 1/2] device property: fwnode->secondary may contain ERR_PTR(-ENODEV)

This fixes BUG that is trickered when fwnode->secondary is not null, but has ERR_PTR(-ENODEV) instead. BUG: unable to handle kernel paging request at ffed IP: [] __fwnode_property_read_string+0x26/0x160 PGD 200e067 PUD 2010067 PMD 0 Oops: [#1] SMP KASAN Modules linked in: dwc3_pci

[PATCH 0/2] device property: fix for couple of bugs

Hi, The fwnode->secondary is causing problems when a property_set is providing the primary fwnode. Both of these fixes are a bit clumsy looking IMO, but I didn't have better ideas. I think the second one fixing the use-after-free bug should ideally be taken care of in set_secondary_fwnode() inste

Re: [PATCH 1/4] net: ethernet: dwmac: add Ethernet glue logic for stm32 chip

2016-02-13 14:48 GMT+01:00 Joachim Eastwood : > On 3 February 2016 at 15:54, Alexandre TORGUE > wrote: >> stm324xx family chips support Synopsys MAC 3.510 IP. >> This patch adds settings for logical glue logic: >> -clocks >> -mode selection MII or RMII. >> >> Signed-off-by: Alexandre TORGUE >> >

Good Day,,,

Good Day, Please accept my apologies for writing you a surprise letter.I am Mr Bakhari Abaas Issa, account Manager with an investment bank here in Burkina Faso. I have a very important business I want to discuss with you.There is a draft account opened in my firm by a long-time client of our ban

[PATCH 03/61] gpio: Add missing devm_gpio_ wrapper in devres.txt

Add following missing devm wrappers in file devrs.txt under list of managed interfaces. devm_gpio_request() devm_gpio_request_one() devm_gpio_free() Signed-off-by: Laxman Dewangan --- Documentation/driver-model/devres.txt | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Documentation

[PATCH 06/61] gpio: adp5520: Use devm_gpiochip_add_data() for gpio registration

Use devm_gpiochip_add_data() for GPIO registration and remove the call for gpiochip_remove() from error path. Also remove the need of driver callback .remove. Signed-off-by: Laxman Dewangan Cc: Michael Hennerich --- drivers/gpio/gpio-adp5520.c | 13 + 1 file changed, 1 insertion(+)

[PATCH 20/61] gpio: ge: Use devm_gpiochip_add_data() for gpio registration

Use devm_gpiochip_add_data() for GPIO registration. Signed-off-by: Laxman Dewangan --- drivers/gpio/gpio-ge.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpio/gpio-ge.c b/drivers/gpio/gpio-ge.c index cbbec83..8650b29 100644 --- a/drivers/gpio/gpio-ge.c +++ b/drive

[PATCH 02/61] gpio: Add resource management devm_gpio_chip_{add_data,remove}

Add devm wrappers for the gpiochip_add_data() and gpiochip_remove(). Signed-off-by: Laxman Dewangan --- Documentation/driver-model/devres.txt | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Documentation/driver-model/devres.txt b/Documentation/driver-model/devres.txt index 831a536..8d8f94

Re: [PATCH V3 0/5] clk: support clocks which requires parent clock on during operation

[0.00] WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:3382 lock_release+0x2f8/0x334() [0.00] releasing a pinned lock [0.00] Modules linked in: [0.00] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.5.0-rc5-next-20160222 #256 [0.00] Hardware name: Freesc

Re: [alsa-devel] [PATCH v2] ASoC: wm9713: fix regmap free path

On 02/20/2016 08:44 PM, Robert Jarzmik wrote: > In the conversion to regmap, I assumed that the 2 following functions > was working symetrically: > - snd_soc_codec_init_regmap() > - snd_soc_codec_exit_regmap(codec) > > As a mater of fact with the current code the regmap is freed twice > because

[PATCH v5 02/20] kthread: Allow to call __kthread_create_on_node() with va_list args

kthread_create_on_node() implements a bunch of logic to create the kthread. It is already called by kthread_create_on_cpu(). We are going to extend the kthread worker API and will need to call kthread_create_on_node() with va_list args there. This patch does only a refactoring and does not modify

[PATCH v5 07/20] kthread: Initial support for delayed kthread work

We are going to use kthread_worker more widely and delayed works will be pretty useful. The implementation is inspired by workqueues. It uses a timer to queue the work after the requested delay. If the delay is zero, the work is queued immediately. In compare with workqueues, each work is associa

[PATCH v5 05/20] kthread: Add destroy_kthread_worker()

The current kthread worker users call flush() and stop() explicitly. This function drains the worker, stops it, and frees the kthread_worker struct in one call. It is supposed to be used together with create_kthread_worker*() that allocates struct kthread_worker. Also note that drain() correctly

[PATCH v5 04/20] kthread: Add drain_kthread_worker()

flush_kthread_worker() returns when the currently queued works are proceed. But some other works might have been queued in the meantime. This patch adds drain_kthread_worker() that is inspired by drain_workqueue(). It returns when the queue is completely empty and warns when it takes too long. Th

[PATCH v5 10/20] kthread: Better support freezable kthread workers

This patch allows to make kthread worker freezable via a new @flags parameter. It will allow to avoid an init work in some kthreads. It currently does not affect the function of kthread_worker_fn() but it might help to do some optimization or fixes eventually. I currently do not know about any ot

[PATCH v5 08/20] kthread: Allow to cancel kthread work

We are going to use kthread workers more widely and sometimes we will need to make sure that the work is neither pending nor running. This patch implements cancel_*_sync() operations as inspired by workqueues. Well, we are synchronized against the other operations via the worker lock, we use del_t

[PATCH v5 14/20] kmemleak: Convert kmemleak kthread into kthread worker API

Kthreads are currently implemented as an infinite loop. Each has its own variant of checks for terminating, freezing, awakening. In many cases it is unclear to say in which state it is and sometimes it is done a wrong way. The plan is to convert kthreads into kthread_worker or workqueues API. It a

[PATCH v5 09/20] kthread: Allow to modify delayed kthread work

There are situations when we need to modify the delay of a delayed kthread work. For example, when the work depends on an event and the initial delay means a timeout. Then we want to queue the work immediately when the event happens. This patch implements mod_delayed_kthread_work() as inspired wor

[PATCH v5 15/20] ipmi: Convert kipmi kthread into kthread worker API

Kthreads are currently implemented as an infinite loop. Each has its own variant of checks for terminating, freezing, awakening. In many cases it is unclear to say in which state it is and sometimes it is done a wrong way. The plan is to convert kthreads into kthread_worker or workqueues API. It a

[PATCH v5 12/20] ring_buffer: Convert benchmark kthreads into kthread worker API

Kthreads are currently implemented as an infinite loop. Each has its own variant of checks for terminating, freezing, awakening. In many cases it is unclear to say in which state it is and sometimes it is done a wrong way. The plan is to convert kthreads into kthread_worker or workqueues API. It a

[PATCH v5 17/20] memstick/r592: Better synchronize debug messages in r592_io kthread

There is an attempt to print debug messages when the kthread is waken and when it goes into sleep. It does not work well because the spin lock does not guard all manipulations with the thread state. I did not find a way how to print a message when the kthread really goes into sleep. Instead, I add

[PATCH v5 16/20] IB/fmr_pool: Convert the cleanup thread into kthread worker API

Kthreads are currently implemented as an infinite loop. Each has its own variant of checks for terminating, freezing, awakening. In many cases it is unclear to say in which state it is and sometimes it is done a wrong way. The plan is to convert kthreads into kthread_worker or workqueues API. It a

[PATCH v5 20/20] thermal/intel_powerclamp: Convert the kthread to kthread worker API

Kthreads are currently implemented as an infinite loop. Each has its own variant of checks for terminating, freezing, awakening. In many cases it is unclear to say in which state it is and sometimes it is done a wrong way. The plan is to convert kthreads into kthread_worker or workqueues API. It a

[PATCH v5 18/20] memstick/r592: convert r592_io kthread into kthread worker API

Kthreads are currently implemented as an infinite loop. Each has its own variant of checks for terminating, freezing, awakening. In many cases it is unclear to say in which state it is and sometimes it is done a wrong way. The plan is to convert kthreads into kthread_worker or workqueues API. It a

[PATCH v5 19/20] thermal/intel_powerclamp: Remove duplicated code that starts the kthread

This patch removes a code duplication. It does not modify the functionality. Signed-off-by: Petr Mladek CC: Zhang Rui CC: Eduardo Valentin CC: Jacob Pan CC: linux...@vger.kernel.org Acked-by: Jacob Pan --- drivers/thermal/intel_powerclamp.c | 45 +- 1 file

Re: [PATCH v3 1/5] ACPI: change __init to __ref for early_acpi_os_unmap_memory()

Hi, On 02/22/2016 05:24 AM, Zheng, Lv wrote: > Hi, > >> From: Aleksey Makarov [mailto:aleksey.maka...@linaro.org] >> Subject: Re: [PATCH v3 1/5] ACPI: change __init to __ref for >> early_acpi_os_unmap_memory() >> >> Hi Lv, >> >> On 02/19/2016 05:58 AM, Zheng, Lv wrote: >>> Hi, >>> From: Pet

Re: [PATCH v6 10/12] arm-cci: CCI-500: Work around PMU counter writes

On Mon, Jan 25, 2016 at 11:21:15AM +, Suzuki K. Poulose wrote: > The CCI PMU driver sets the event counter to the half of the maximum > value(2^31) it can count before we start the counters via > pmu_event_set_period(). This is done to give us the best chance to > handle the overflow interrupt,

[PATCH v5 03/20] kthread: Add create_kthread_worker*()

Kthread workers are currently created using the classic kthread API, namely kthread_run(). kthread_worker_fn() is passed as the @threadfn parameter. This patch defines create_kthread_worker() and create_kthread_worker_on_cpu() functions that hide implementation details. They enforce using kthread

Re: [PATCH V3 2/2] sched: idle: IRQ based next prediction for idle period

Hi Daniel, On 02/16/2016 09:13 PM, Daniel Lezcano wrote: > + > +/** > + * sched_idle_next_wakeup - Predict the next wakeup on the current cpu > + * > + * The next event on the cpu is based on a statistic approach of the > + * interrupt events and the timer deterministic value. From the timer > + *

[PATCH v5 01/20] kthread/smpboot: Do not park in kthread_create_on_cpu()

kthread_create_on_cpu() was added by the commit 2a1d446019f9a5983e ("kthread: Implement park/unpark facility"). It is currently used only when enabling new CPU. For this purpose, the newly created kthread has to be parked. The CPU binding is a bit tricky. The kthread is parked when the CPU has not

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

Hi Yury, Thank you for review/suggestions. I will address it all in the next version except for... On 02/21/2016 12:42 PM, Yury Norov wrote: > On Mon, Feb 15, 2016 at 09:05:26PM +0300, Aleksey Makarov wrote: >> 'ARM Server Base Boot Requiremets' [1] mentions SPCR (Serial Port >> Console Redirec

[PATCH v5 00/20] kthread: Use kthread worker API more widely

My intention is to make it easier to manipulate and maintain kthreads. Especially, I want to replace all the custom main cycles with a generic one. Also I want to make the kthreads sleep in a consistent state in a common place when there is no work. My first attempt was with a brand new API (itera

[PATCH v5 06/20] kthread: Detect when a kthread work is used by more workers

Nothing currently prevents a work from queuing for a kthread worker when it is already running on another one. This means that the work might run in parallel on more workers. Also some operations, e.g. flush or drain are not reliable. This problem will be even more visible after we add cancel_kthr

[PATCH v5 11/20] mm/huge_page: Convert khugepaged() into kthread worker API

Kthreads are currently implemented as an infinite loop. Each has its own variant of checks for terminating, freezing, awakening. In many cases it is unclear to say in which state it is and sometimes it is done a wrong way. The plan is to convert kthreads into kthread_worker or workqueues API. It a

[PATCH v5 13/20] hung_task: Convert hungtaskd into kthread worker API

Kthreads are currently implemented as an infinite loop. Each has its own variant of checks for terminating, freezing, awakening. In many cases it is unclear to say in which state it is and sometimes it is done a wrong way. The plan is to convert kthreads into kthread_worker or workqueues API. It a

Re: [PATCH 1/5] perf tools: Fix assertion failure on dynamic entry

Em Sun, Feb 21, 2016 at 06:37:32PM +0100, Jiri Olsa escreveu: > On Sun, Feb 21, 2016 at 11:22:34PM +0900, Namhyung Kim wrote: > > The dynamic entry is created for each field in a tracepoint event. > > Since they have no fixed hpp format index, it should skip when > > perf_hpp__reset_width() is call

Re: [PATCH 2/8] of/serial: move earlycon early_param handling to serial

Hi Leif, [auto build test ERROR on pm/linux-next] [also build test ERROR on v4.5-rc5 next-20160222] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https://github.com/0day-ci/linux/commits/Aleksey-Makarov/arm64-move-acpi-dt-decision

[PATCH net v2] r8169:fix "rtl_counters_cond == 1 (loop: 1000, delay: 10)" log spam.

There will be a log spam when there is no cable plugged. Please refer to following links. https://bugzilla.kernel.org/show_bug.cgi?id=104351 https://bugzilla.kernel.org/show_bug.cgi?id=107421 This issue is caused by runtime power management. When there is no cable plugged, the driver will be suspe

Re: [PATCH v6 08/12] __cci_pmu_enable: Make counter sync optional

On Mon, Jan 25, 2016 at 11:21:13AM +, Suzuki K. Poulose wrote: > On CCI-500 writing to a counter requires turning the PMU on. So, > syncing the counter state should not be performed for such special cases, > while turning the PMU on. This patch makes the 'sync' operation based > on an input par

Re: [PATCH v6 10/12] arm-cci: CCI-500: Work around PMU counter writes

A couple more comments for things i just realised: > + /* > + * Now that all the counters are disabled, we can safely turn the PMU > on, > + * without syncing the status of the counters > + */ > + __cci_pmu_enable(cci_pmu, CCI_CNTRS_NOSYNC); As per my other comment, __cci_

Re: [PATCH 06/54] perf tools: Add API to config maps in bpf object

Em Mon, Feb 22, 2016 at 12:05:36PM +0800, Wangnan (F) escreveu: > > > On 2016/2/19 21:53, Arnaldo Carvalho de Melo wrote: > >Sorry for the top post, but the message below didn't made it thru due to > >local problems as I recently switched notebooks, my postfix setup barfed > >this one :-\ > > > >

Re: [PATCH v6 00/12] arm-cci: PMU driver updates

On Mon, Jan 25, 2016 at 11:21:05AM +, Suzuki K. Poulose wrote: > Suzuki K. Poulose (11): > arm-cci: Group writes to counter > arm-cci: Refactor CCI PMU enable/disable methods > arm-cci: Delay PMU counter writes to pmu::pmu_enable > arm-cci: write_counter: Remove redundant check > arm-

[PATCH 0/8] Remove CURRENT_TIME and CURRENT_TIME_SEC - PART 2

Introduction This patch series is aimed at getting rid of CURRENT_TIME and CURRENT_TIME_SEC macros. The idea for the series evolved from my discussions with Arnd Bergmann. This was originally part of the RFC series[2]: https://lkml.org/lkml/2016/1/7/20 (under discussion). Dave Chinner suggested

Re: [PATCH v4 5/8] [Media] vcodec: mediatek: Add Mediatek V4L2 Video Encoder Driver

Hi Hans, On Sat, 2016-02-20 at 10:18 +0100, Hans Verkuil wrote: > On 02/20/2016 10:11 AM, tiffany lin wrote: > > Hi Hans, > > > > On Tue, 2016-02-16 at 08:44 +0100, Hans Verkuil wrote: > >> On 02/16/2016 07:37 AM, tiffany lin wrote: > > + > > +const struct v4l2_ioctl_ops mtk_venc_ioctl_op

Re: [RFC PATCH] drivers: ata: Read Rx water mark value from device-tree

On Monday 22 February 2016 10:53:11 Anurag Kumar Vulisha wrote: > > > > > > > How would a hardware integrator know which value is right for a particular > > SoC? > > > > Could it be keyed off the hardware ID? Could the bootloader perhaps set an > > appropriate value in the AHCI_VEND_PTC register

Re: [PATCH] fpga manager: Add hardware dependency to Zynq driver

On 22.2.2016 14:42, Jean Delvare wrote: > The Zynq FPGA manager driver serves no purpose on other architectures > so hide it unless build-testing. > > Signed-off-by: Jean Delvare > Cc: Alan Tull > Cc: Moritz Fischer > Cc: Michal Simek > Cc: "Sören Brinkmann" > --- > Michal, Sören, I'm not sur

[PATCH 1/8] fs: debugfs: Replace CURRENT_TIME by current_fs_time()

CURRENT_TIME macro is not appropriate for filesystems as it doesn't use the right granularity for filesystem timestamps. Use current_fs_time() instead. Signed-off-by: Deepa Dinamani Cc: Greg Kroah-Hartman --- fs/debugfs/inode.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git

[PATCH 2/8] fs: logfs: Replace CURRENT_TIME by current_fs_time()

CURRENT_TIME macro is not appropriate for filesystems as it doesn't use the right granularity for filesystem timestamps. Use current_fs_time() instead. Signed-off-by: Deepa Dinamani Cc: Joern Engel Cc: Prasad Joshi Cc: lo...@logfs.org --- fs/logfs/dir.c | 11 +++ fs/logfs/file.c

[PATCH 3/8] fs: devpts: Replace CURRENT_TIME by current_fs_time()

CURRENT_TIME macro is not appropriate for filesystems as it doesn't use the right granularity for filesystem timestamps. Use current_fs_time() instead. Signed-off-by: Deepa Dinamani Cc: Peter Hurley Cc: Al Viro Cc: Josh Triplett Cc: Greg Kroah-Hartman Cc: Andrew Morton --- fs/devpts/inode.c

[PATCH 4/8] fs: configfs: Replace CURRENT_TIME by current_fs_time()

CURRENT_TIME macro is not appropriate for filesystems as it doesn't use the right granularity for filesystem timestamps. Use current_fs_time() instead. Signed-off-by: Deepa Dinamani Cc: Joel Becker Cc: stoph Hellwig --- fs/configfs/inode.c | 8 +--- 1 file changed, 5 insertions(+), 3 delet

block: NULL ptr deref in bio_copy_user_iov

Hi all, I've hit the following NULL ptr deref while fuzzing with trinity inside a kvmtool guest running the latest -next kernel: [ 1274.081122] BUG: unable to handle kernel NULL pointer dereference at (null) [ 1274.081140] IP: __memcpy (arch/x86/lib/memcpy_64.S:36) [ 1274.081154] PGD

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