Re: [PATCH 2/3] phy: rockchip-emmc: Be tolerant to card clock of 0 in power on

Ulf, On Saturday 23 July 2016 03:09 PM, Ulf Hansson wrote: > On 29 June 2016 at 17:18, Doug Anderson wrote: >> Kishon, >> >> On Wed, Jun 29, 2016 at 6:49 AM, Kishon Vijay Abraham I >> wrote: >>> Hi, >>> >>> On Monday 27 June 2016 11:09 PM, Douglas Anderson

Re: [PATCH 2/3] phy: rockchip-emmc: Be tolerant to card clock of 0 in power on

Ulf, On Saturday 23 July 2016 03:09 PM, Ulf Hansson wrote: > On 29 June 2016 at 17:18, Doug Anderson wrote: >> Kishon, >> >> On Wed, Jun 29, 2016 at 6:49 AM, Kishon Vijay Abraham I >> wrote: >>> Hi, >>> >>> On Monday 27 June 2016 11:09 PM, Douglas Anderson wrote: It's possible that there

[PATCH v5 2/2] QE: remove PPCisms for QE

QE was supported on PowerPC, and dependent on PPC, Now it is supported on other platforms. so remove PPCisms. Signed-off-by: Zhao Qiang --- Changes for v2: - na Changes for v3: - add NO_IRQ Changes for v4: - modify spin_event_timeout to opencoded

[PATCH v5 2/2] QE: remove PPCisms for QE

QE was supported on PowerPC, and dependent on PPC, Now it is supported on other platforms. so remove PPCisms. Signed-off-by: Zhao Qiang --- Changes for v2: - na Changes for v3: - add NO_IRQ Changes for v4: - modify spin_event_timeout to opencoded timeout loop -

Re: [RFC PATCH v3 00/13] ACPI IORT ARM SMMU v3 support

Hi On Wed, Jul 20, 2016 at 12:23:22PM +0100, Lorenzo Pieralisi wrote: > This RFC patch series is v3 of a previous posting: > > https://lkml.org/lkml/2016/6/7/523 > > v2 -> v3 > - Rebased on top of dependencies series [1][2][3](v4.7-rc3) > - Added back reliance on ACPI early probing

Re: [RFC PATCH v3 00/13] ACPI IORT ARM SMMU v3 support

Hi On Wed, Jul 20, 2016 at 12:23:22PM +0100, Lorenzo Pieralisi wrote: > This RFC patch series is v3 of a previous posting: > > https://lkml.org/lkml/2016/6/7/523 > > v2 -> v3 > - Rebased on top of dependencies series [1][2][3](v4.7-rc3) > - Added back reliance on ACPI early probing

Re: [PATCH 3.12 28/88] netfilter: x_tables: validate targets of jumps

On Thu, Jul 21, 2016 at 09:00:33PM +0200, Jiri Slaby wrote: > On 07/21/2016, 08:56 PM, Greg KH wrote: > > On Thu, Jul 21, 2016 at 08:36:18AM +0200, Jiri Slaby wrote: > >> On 07/14/2016, 10:15 AM, Jiri Slaby wrote: > >>> From: Florian Westphal > >>> > >>> 3.12-stable review patch.

Re: [PATCH 3.12 28/88] netfilter: x_tables: validate targets of jumps

On Thu, Jul 21, 2016 at 09:00:33PM +0200, Jiri Slaby wrote: > On 07/21/2016, 08:56 PM, Greg KH wrote: > > On Thu, Jul 21, 2016 at 08:36:18AM +0200, Jiri Slaby wrote: > >> On 07/14/2016, 10:15 AM, Jiri Slaby wrote: > >>> From: Florian Westphal > >>> > >>> 3.12-stable review patch. If anyone has

RE: Why does BIOS assign memory to 16 byte BAR

> Subject: RE: Why does BIOS assign memory to 16 byte BAR > > > Subject: Re: Why does BIOS assign memory to 16 byte BAR > > > > On Fri, Jul 22, 2016 at 10:15:46AM -0500, Bjorn Helgaas wrote: > > > Hi Bharat, > > > > > > On Fri, Jul 22, 2016 at 09:24:22AM +, Bharat Kumar Gogada wrote: > > > >

RE: Why does BIOS assign memory to 16 byte BAR

> Subject: RE: Why does BIOS assign memory to 16 byte BAR > > > Subject: Re: Why does BIOS assign memory to 16 byte BAR > > > > On Fri, Jul 22, 2016 at 10:15:46AM -0500, Bjorn Helgaas wrote: > > > Hi Bharat, > > > > > > On Fri, Jul 22, 2016 at 09:24:22AM +, Bharat Kumar Gogada wrote: > > > >

Re: [PATCH] PM / OPP: optimize dev_pm_opp_set_rate() a bit

Dear all, On Fri, 22 Jul 2016 22:30:53 +0800 kbuild test robot wrote: > Hi, > > [auto build test WARNING on pm/linux-next] > [also build test WARNING on v4.7-rc7 next-20160722] > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the system] > > url:

Re: [PATCH] PM / OPP: optimize dev_pm_opp_set_rate() a bit

Dear all, On Fri, 22 Jul 2016 22:30:53 +0800 kbuild test robot wrote: > Hi, > > [auto build test WARNING on pm/linux-next] > [also build test WARNING on v4.7-rc7 next-20160722] > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the system] > > url:

Re: [PATCH] net: neigh: disallow state transition DELAY->STALE in neigh_update()

Hi, Chunhui He wrote: > Hi, > > On Fri, 22 Jul 2016 10:20:01 +0300 (EEST), Julian Anastasov > wrote: >> >> Hello, >> >> On Thu, 21 Jul 2016, Chunhui He wrote: >> >>> If neigh entry was CONNECTED and address is not changed, and if new state is >>> STALE, entry state will not

Re: [PATCH] net: neigh: disallow state transition DELAY->STALE in neigh_update()

Hi, Chunhui He wrote: > Hi, > > On Fri, 22 Jul 2016 10:20:01 +0300 (EEST), Julian Anastasov > wrote: >> >> Hello, >> >> On Thu, 21 Jul 2016, Chunhui He wrote: >> >>> If neigh entry was CONNECTED and address is not changed, and if new state is >>> STALE, entry state will not change.

[PATCH v2] PM / OPP: optimize dev_pm_opp_set_rate() performance a bit

In dev_pm_opp_set_rate(), _find_opp_table() is called 4 times: once by _get_opp_clk(), once by dev_pm_opp_set_rate() itself, and twice by dev_pm_opp_find_freq_ceil(). If there are several opp_tables in the system, three times of opp table finding is a big waste. This patch reduced the call of

[PATCH v2] PM / OPP: optimize dev_pm_opp_set_rate() performance a bit

In dev_pm_opp_set_rate(), _find_opp_table() is called 4 times: once by _get_opp_clk(), once by dev_pm_opp_set_rate() itself, and twice by dev_pm_opp_find_freq_ceil(). If there are several opp_tables in the system, three times of opp table finding is a big waste. This patch reduced the call of

Re: [PATCH] PM / OPP: optimize dev_pm_opp_set_rate() a bit

Dear Viresh, On Fri, 22 Jul 2016 09:21:51 -0700 Viresh Kumar wrote: > On 22-07-16, 20:42, Jisheng Zhang wrote: > > static int _set_opp_voltage(struct device *dev, struct regulator *reg, > > unsigned long u_volt, unsigned long u_volt_min, > >

Re: [PATCH] PM / OPP: optimize dev_pm_opp_set_rate() a bit

Dear Viresh, On Fri, 22 Jul 2016 09:21:51 -0700 Viresh Kumar wrote: > On 22-07-16, 20:42, Jisheng Zhang wrote: > > static int _set_opp_voltage(struct device *dev, struct regulator *reg, > > unsigned long u_volt, unsigned long u_volt_min, > >

Re: [PATCH net-next v4] cdc_ether: Improve ZTE MF823/831/910 handling

From: Kristian Evensen Date: Thu, 21 Jul 2016 11:10:06 +0200 > The firmware in several ZTE devices (at least the MF823/831/910 > modems/mifis) use OS fingerprinting to determine which type of device to > export. In addition, these devices export a REST API which can

Re: [PATCH net-next v4] cdc_ether: Improve ZTE MF823/831/910 handling

From: Kristian Evensen Date: Thu, 21 Jul 2016 11:10:06 +0200 > The firmware in several ZTE devices (at least the MF823/831/910 > modems/mifis) use OS fingerprinting to determine which type of device to > export. In addition, these devices export a REST API which can be used to > control the type

Re: [PATCH v2] include: mman: Use bool instead of int for the return value of arch_validate_prot

cheng...@emindsoft.com.cn writes: > From: Chen Gang > > For pure bool function's return value, bool is a little better more or > less than int. > > Signed-off-by: Chen Gang > --- > arch/powerpc/include/asm/mman.h | 8 >

Re: [PATCH v2] include: mman: Use bool instead of int for the return value of arch_validate_prot

cheng...@emindsoft.com.cn writes: > From: Chen Gang > > For pure bool function's return value, bool is a little better more or > less than int. > > Signed-off-by: Chen Gang > --- > arch/powerpc/include/asm/mman.h | 8 > include/linux/mman.h| 2 +- > 2 files changed, 5

Re: [PATCH 0/2] PCI: altera: fix link retrain

On Sat, Jul 23, 2016 at 5:07 AM, Bjorn Helgaas wrote: > > On Tue, Jun 21, 2016 at 04:53:11PM +0800, Ley Foon Tan wrote: > > This 2 patches fix the issue before and after retrain link. > > > > Ley Foon Tan (2): > > PCI: altera: check link status before retrain link > > PCI:

Re: [PATCH 0/2] PCI: altera: fix link retrain

On Sat, Jul 23, 2016 at 5:07 AM, Bjorn Helgaas wrote: > > On Tue, Jun 21, 2016 at 04:53:11PM +0800, Ley Foon Tan wrote: > > This 2 patches fix the issue before and after retrain link. > > > > Ley Foon Tan (2): > > PCI: altera: check link status before retrain link > > PCI: altera: Polling for

Re: [PATCH net-next V3] net: ena: Add a driver for Amazon Elastic Network Adapters (ENA)

On Tue, Jul 19, 2016 at 10:49:57AM -0700, Joe Perches wrote: > On Tue, 2016-07-19 at 20:26 +0300, Leon Romanovsky wrote: > > On Tue, Jul 19, 2016 at 02:09:25PM +0300, Netanel Belgazal wrote: > > > This is the debugging message interface. > > >

Re: [PATCH net-next V3] net: ena: Add a driver for Amazon Elastic Network Adapters (ENA)

On Tue, Jul 19, 2016 at 10:49:57AM -0700, Joe Perches wrote: > On Tue, 2016-07-19 at 20:26 +0300, Leon Romanovsky wrote: > > On Tue, Jul 19, 2016 at 02:09:25PM +0300, Netanel Belgazal wrote: > > > This is the debugging message interface. > > >

linux-next: manual merge of the nvdimm tree with the kvm tree

Hi Dan, Today's linux-next merge of the nvdimm tree got a conflict in: arch/x86/kvm/vmx.c between commits: 64672c95ea4c ("kvm: vmx: hook preemption timer support") 37e4c997dadf ("KVM: VMX: validate individual bits of guest MSR_IA32_FEATURE_CONTROL") from the kvm tree and commit:

linux-next: manual merge of the nvdimm tree with the kvm tree

Hi Dan, Today's linux-next merge of the nvdimm tree got a conflict in: arch/x86/kvm/vmx.c between commits: 64672c95ea4c ("kvm: vmx: hook preemption timer support") 37e4c997dadf ("KVM: VMX: validate individual bits of guest MSR_IA32_FEATURE_CONTROL") from the kvm tree and commit:

Re: [PATCH] [media] cxd2841er: avoid misleading gcc warning

Hello Arnd, thanks for patch. it looks ok. Acked-by: Abylay Ospan 2016-07-13 16:42 GMT-04:00 Arnd Bergmann : > The addition of jump label support in dynamic_debug caused an unexpected > warning in exactly one file in the kernel: > >

Re: [PATCH] [media] cxd2841er: avoid misleading gcc warning

Hello Arnd, thanks for patch. it looks ok. Acked-by: Abylay Ospan 2016-07-13 16:42 GMT-04:00 Arnd Bergmann : > The addition of jump label support in dynamic_debug caused an unexpected > warning in exactly one file in the kernel: > > drivers/media/dvb-frontends/cxd2841er.c: In function

Re: [RFC/PATCH 00/14] split exception table content out of module.h into extable.h

On Sun, Jul 24, 2016 at 8:42 PM, Paul Gortmaker wrote: > > While doing an audit looking for unnecessary instances of module.h > inclusion across arch/x86/ I found a significant number of includes > of module.h were for things like search_exception_table and friends.

Re: [RFC/PATCH 00/14] split exception table content out of module.h into extable.h

On Sun, Jul 24, 2016 at 8:42 PM, Paul Gortmaker wrote: > > While doing an audit looking for unnecessary instances of module.h > inclusion across arch/x86/ I found a significant number of includes > of module.h were for things like search_exception_table and friends. > > For historical reasons

Re: linux-next: build failure after merge of the sh tree

Hi Rich, On Sun, 24 Jul 2016 23:57:30 -0400 Rich Felker wrote: > > If it's acceptable I'll rebase this change into sh for-next and the > patch I send to the subsystem maintainer. Sure. -- Cheers, Stephen Rothwell

Re: linux-next: build failure after merge of the sh tree

Hi Rich, On Sun, 24 Jul 2016 23:57:30 -0400 Rich Felker wrote: > > If it's acceptable I'll rebase this change into sh for-next and the > patch I send to the subsystem maintainer. Sure. -- Cheers, Stephen Rothwell

Re: linux-next: manual merge of the tip tree with the sh tree

Hi Rich, On Sun, 24 Jul 2016 23:55:03 -0400 Rich Felker wrote: > > On Sun, Jul 24, 2016 at 03:13:42PM +1000, Stephen Rothwell wrote: > > > > Today's linux-next merge of the tip tree got a conflict in: > > > > arch/sh/include/asm/spinlock.h > > > > between commit: > > > >

Re: linux-next: manual merge of the tip tree with the sh tree

Hi Rich, On Sun, 24 Jul 2016 23:55:03 -0400 Rich Felker wrote: > > On Sun, Jul 24, 2016 at 03:13:42PM +1000, Stephen Rothwell wrote: > > > > Today's linux-next merge of the tip tree got a conflict in: > > > > arch/sh/include/asm/spinlock.h > > > > between commit: > > > > 2da83dfce7df

[PATCH v2 3/5] pstore: support multiple pmsg instances

From: Hiraku Toyooka This enables pmsg to deal with multiple instances. One possible use is content priority control on limited persistent store space. By using different buffers, we can prevent important messages from being overwritten by less important messages.

[PATCH v2 5/5] selftests/pstore: add testcases for multiple pmsg instances

From: Hiraku Toyooka To test multiple pmsg, we should check that /dev/pmsg[N] (N > 0) is available. After reboot, we should check that pmsg-[backend]-[N] which keeps content is detected even if pmsg-[backend]-[N-M] (0 < M <= N) doesn't exist due to lack of

[PATCH v2 3/5] pstore: support multiple pmsg instances

From: Hiraku Toyooka This enables pmsg to deal with multiple instances. One possible use is content priority control on limited persistent store space. By using different buffers, we can prevent important messages from being overwritten by less important messages. When pstore backend module

[PATCH v2 5/5] selftests/pstore: add testcases for multiple pmsg instances

From: Hiraku Toyooka To test multiple pmsg, we should check that /dev/pmsg[N] (N > 0) is available. After reboot, we should check that pmsg-[backend]-[N] which keeps content is detected even if pmsg-[backend]-[N-M] (0 < M <= N) doesn't exist due to lack of contents. So this adds the following

[PATCH v2 1/5] ramoops: use persistent_ram_free() instead of kfree() for freeing prz

From: Hiraku Toyooka persistent_ram_zone(=prz) structures are allocated by persistent_ram_new(), which includes vmap() or ioremap(). But they are currently freed by kfree(). This uses persistent_ram_free() for correct this asymmetry usage. Signed-off-by: Hiraku

[PATCH v2 2/5] ramoops: introduce generic init/free functions for prz

From: Hiraku Toyooka We modifies initialization and freeing code for prz for generic usage. This change * add generic function __ramoops_init_prz() to reduce redundancy between ramoops_init_prz() and ramoops_init_przs(). * rename 'przs' member in struct

[PATCH v2 0/5] pstore: ramoops: support multiple pmsg instances

The following series implements multiple pmsg. This feature allows userspace program to control individual content aging or priority. If a pstore backend module(e.g. ramoops) requires the multiple pmsg instances when registering itself to pstore, multiple /dev/pmsg[ID] are created. Writes to each

[PATCH v2 4/5] ramoops: support multiple pmsg instances

From: Hiraku Toyooka This enables ramoops to deal with multiple pmsg instances. A User can configure the size of each buffers by its module parameter as follows. pmsg_size=0x1000,0x2000,... Then, the ramoops allocates multiple buffers and tells the number of

[PATCH v2 1/5] ramoops: use persistent_ram_free() instead of kfree() for freeing prz

From: Hiraku Toyooka persistent_ram_zone(=prz) structures are allocated by persistent_ram_new(), which includes vmap() or ioremap(). But they are currently freed by kfree(). This uses persistent_ram_free() for correct this asymmetry usage. Signed-off-by: Hiraku Toyooka Signed-off-by: Nobuhiro

[PATCH v2 2/5] ramoops: introduce generic init/free functions for prz

From: Hiraku Toyooka We modifies initialization and freeing code for prz for generic usage. This change * add generic function __ramoops_init_prz() to reduce redundancy between ramoops_init_prz() and ramoops_init_przs(). * rename 'przs' member in struct ramoops_context to 'dprzs' so that

[PATCH v2 0/5] pstore: ramoops: support multiple pmsg instances

The following series implements multiple pmsg. This feature allows userspace program to control individual content aging or priority. If a pstore backend module(e.g. ramoops) requires the multiple pmsg instances when registering itself to pstore, multiple /dev/pmsg[ID] are created. Writes to each

[PATCH v2 4/5] ramoops: support multiple pmsg instances

From: Hiraku Toyooka This enables ramoops to deal with multiple pmsg instances. A User can configure the size of each buffers by its module parameter as follows. pmsg_size=0x1000,0x2000,... Then, the ramoops allocates multiple buffers and tells the number of buffers to pstore to create

Re: linux-next: build failure after merge of the sh tree

On Sun, Jul 24, 2016 at 05:55:01PM +1000, Stephen Rothwell wrote: > Hi Rich, > > After merging the sh tree, today's linux-next build (powerpc allyesconfig) > failed like this: > > drivers/clocksource/jcore-pit.c:145:20: error: conflicting types for > 'timer_interrupt' > static irqreturn_t

Re: linux-next: manual merge of the tip tree with the sh tree

On Sun, Jul 24, 2016 at 03:13:42PM +1000, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the tip tree got a conflict in: > > arch/sh/include/asm/spinlock.h > > between commit: > > 2da83dfce7df ("sh: add J2 atomics using the cas.l instruction") > > from the sh tree and

Re: linux-next: build failure after merge of the sh tree

On Sun, Jul 24, 2016 at 05:55:01PM +1000, Stephen Rothwell wrote: > Hi Rich, > > After merging the sh tree, today's linux-next build (powerpc allyesconfig) > failed like this: > > drivers/clocksource/jcore-pit.c:145:20: error: conflicting types for > 'timer_interrupt' > static irqreturn_t

Re: linux-next: manual merge of the tip tree with the sh tree

On Sun, Jul 24, 2016 at 03:13:42PM +1000, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the tip tree got a conflict in: > > arch/sh/include/asm/spinlock.h > > between commit: > > 2da83dfce7df ("sh: add J2 atomics using the cas.l instruction") > > from the sh tree and

Re: linux-next: build warning after merge of the sh tree

On Sun, Jul 24, 2016 at 11:00:12AM +1000, Stephen Rothwell wrote: > Hi Rich, > > After merging the sh tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > WARNING: modpost: missing MODULE_LICENSE() in drivers/spi/spi-jcore.o > > Introduced by commit > >

Re: linux-next: build warning after merge of the sh tree

On Sun, Jul 24, 2016 at 11:00:12AM +1000, Stephen Rothwell wrote: > Hi Rich, > > After merging the sh tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > WARNING: modpost: missing MODULE_LICENSE() in drivers/spi/spi-jcore.o > > Introduced by commit > >

[PATCH 14/14] module.h: remove extable.h include now users have migrated

With hopefully most/all users of module.h that were looking for exception table functions moved over to the new extable.h header, we can remove the back-compat include that let us transition without introducing build regressions. Cc: Rusty Russell Cc: Andrew Morton

[RFC/PATCH 00/14] split exception table content out of module.h into extable.h

[RFC: Not looking for detailed review given the merge window is open. As long as nobody thinks the general idea is horrible, I'll expand into more fringe arch and resend in 2wks and get it added then to linux-next.] While doing an audit looking for unnecessary instances of module.h inclusion

[PATCH 11/14] alpha: migrate exception table users off module.h and onto extable.h

These files were only including module.h for exception table related functions. We've now separated that content out into its own file "extable.h" so now move over to that and avoid all the extra header content in module.h that we don't really need to compile these files. Cc: Richard Henderson

[PATCH 10/14] tile: migrate exception table users off module.h and onto extable.h

These files were only including module.h for exception table related functions. We've now separated that content out into its own file "extable.h" so now move over to that and avoid all the extra header content in module.h that we don't really need to compile these files. Cc: Chris Metcalf

[PATCH 08/14] m68k: migrate exception table users off module.h and onto extable.h

This file was only including module.h for exception table related functions. We've now separated that content out into its own file "extable.h" so now move over to that and avoid all the extra header content in module.h that we don't really need to compile this. Cc: Geert Uytterhoeven

[PATCH 14/14] module.h: remove extable.h include now users have migrated

With hopefully most/all users of module.h that were looking for exception table functions moved over to the new extable.h header, we can remove the back-compat include that let us transition without introducing build regressions. Cc: Rusty Russell Cc: Andrew Morton Cc: Linus Torvalds

[RFC/PATCH 00/14] split exception table content out of module.h into extable.h

[RFC: Not looking for detailed review given the merge window is open. As long as nobody thinks the general idea is horrible, I'll expand into more fringe arch and resend in 2wks and get it added then to linux-next.] While doing an audit looking for unnecessary instances of module.h inclusion

[PATCH 11/14] alpha: migrate exception table users off module.h and onto extable.h

These files were only including module.h for exception table related functions. We've now separated that content out into its own file "extable.h" so now move over to that and avoid all the extra header content in module.h that we don't really need to compile these files. Cc: Richard Henderson

[PATCH 10/14] tile: migrate exception table users off module.h and onto extable.h

These files were only including module.h for exception table related functions. We've now separated that content out into its own file "extable.h" so now move over to that and avoid all the extra header content in module.h that we don't really need to compile these files. Cc: Chris Metcalf

[PATCH 08/14] m68k: migrate exception table users off module.h and onto extable.h

This file was only including module.h for exception table related functions. We've now separated that content out into its own file "extable.h" so now move over to that and avoid all the extra header content in module.h that we don't really need to compile this. Cc: Geert Uytterhoeven Cc:

[PATCH 03/14] arm: migrate exception table users off module.h and onto extable.h

These files were only including module.h for exception table related functions. We've now separated that content out into its own file "extable.h" so now move over to that and avoid all the extra header content in module.h that we don't really need to compile these files. Cc: Russell King

[PATCH 04/14] arm64: migrate exception table users off module.h and onto extable.h

These files were only including module.h for exception table related functions. We've now separated that content out into its own file "extable.h" so now move over to that and avoid all the extra header content in module.h that we don't really need to compile these files. Cc: Catalin Marinas

[PATCH 09/14] s390: migrate exception table users off module.h and onto extable.h

These files were only including module.h for exception table related functions. We've now separated that content out into its own file "extable.h" so now move over to that and avoid all the extra header content in module.h that we don't really need to compile these files. The additions of

[PATCH 13/14] core: migrate exception table users off module.h and onto extable.h

These files were including module.h for exception table related functions. We've now separated that content out into its own file "extable.h" so now move over to that and where possible, avoid all the extra header content in module.h that we don't really need to compile these non-modular files.

[PATCH 03/14] arm: migrate exception table users off module.h and onto extable.h

These files were only including module.h for exception table related functions. We've now separated that content out into its own file "extable.h" so now move over to that and avoid all the extra header content in module.h that we don't really need to compile these files. Cc: Russell King Cc:

[PATCH 04/14] arm64: migrate exception table users off module.h and onto extable.h

These files were only including module.h for exception table related functions. We've now separated that content out into its own file "extable.h" so now move over to that and avoid all the extra header content in module.h that we don't really need to compile these files. Cc: Catalin Marinas

[PATCH 09/14] s390: migrate exception table users off module.h and onto extable.h

These files were only including module.h for exception table related functions. We've now separated that content out into its own file "extable.h" so now move over to that and avoid all the extra header content in module.h that we don't really need to compile these files. The additions of

[PATCH 13/14] core: migrate exception table users off module.h and onto extable.h

These files were including module.h for exception table related functions. We've now separated that content out into its own file "extable.h" so now move over to that and where possible, avoid all the extra header content in module.h that we don't really need to compile these non-modular files.

[PATCH 12/14] parisc: migrate exception table users off module.h and onto extable.h

This file was only including module.h for exception table related functions. We've now separated that content out into its own file "extable.h" so now move over to that and avoid all the extra header content in module.h that we don't really need to compile this file. Cc: "James E.J. Bottomley"

[PATCH 02/14] x86: migrate exception table users off module.h and onto extable.h

These files were only including module.h for exception table related functions. We've now separated that content out into its own file "extable.h" so now move over to that and avoid all the extra header content in module.h that we don't really need to compile these files. Cc: Thomas Gleixner

[PATCH 07/14] powerpc: migrate exception table users off module.h and onto extable.h

These files were only including module.h for exception table related functions. We've now separated that content out into its own file "extable.h" so now move over to that and avoid all the extra header content in module.h that we don't really need to compile these files. Cc: Benjamin

[PATCH 12/14] parisc: migrate exception table users off module.h and onto extable.h

This file was only including module.h for exception table related functions. We've now separated that content out into its own file "extable.h" so now move over to that and avoid all the extra header content in module.h that we don't really need to compile this file. Cc: "James E.J. Bottomley"

[PATCH 02/14] x86: migrate exception table users off module.h and onto extable.h

These files were only including module.h for exception table related functions. We've now separated that content out into its own file "extable.h" so now move over to that and avoid all the extra header content in module.h that we don't really need to compile these files. Cc: Thomas Gleixner

[PATCH 07/14] powerpc: migrate exception table users off module.h and onto extable.h

These files were only including module.h for exception table related functions. We've now separated that content out into its own file "extable.h" so now move over to that and avoid all the extra header content in module.h that we don't really need to compile these files. Cc: Benjamin

[PATCH 05/14] mips: migrate exception table users off module.h and onto extable.h

These files were only including module.h for exception table related functions. We've now separated that content out into its own file "extable.h" so now move over to that and avoid all the extra header content in module.h that we don't really need to compile these files. Cc: Ralf Baechle

[PATCH 01/14] exceptions: fork exception table content from module.h into extable.h

For historical reasons (i.e. pre-git) the exception table stuff was buried in the middle of the module.h file. I noticed this while doing an audit for needless includes of module.h and found core kernel files (both arch specific and arch independent) were just including module.h for this. The

[PATCH 06/14] sparc: migrate exception table users off module.h and onto extable.h

These files were only including module.h for exception table related functions. We've now separated that content out into its own file "extable.h" so now move over to that and avoid all the extra header content in module.h that we don't really need to compile these files. Cc: "David S. Miller"

[PATCH 05/14] mips: migrate exception table users off module.h and onto extable.h

These files were only including module.h for exception table related functions. We've now separated that content out into its own file "extable.h" so now move over to that and avoid all the extra header content in module.h that we don't really need to compile these files. Cc: Ralf Baechle Cc:

[PATCH 01/14] exceptions: fork exception table content from module.h into extable.h

For historical reasons (i.e. pre-git) the exception table stuff was buried in the middle of the module.h file. I noticed this while doing an audit for needless includes of module.h and found core kernel files (both arch specific and arch independent) were just including module.h for this. The

[PATCH 06/14] sparc: migrate exception table users off module.h and onto extable.h

These files were only including module.h for exception table related functions. We've now separated that content out into its own file "extable.h" so now move over to that and avoid all the extra header content in module.h that we don't really need to compile these files. Cc: "David S. Miller"

[PATCH v3 7/9] hwmon: (core) Add fan attribute support to new API

Acked-by: Punit Agrawal Reviewed-by: Jonathan Cameron Signed-off-by: Guenter Roeck --- v3: No change v2: No change drivers/hwmon/hwmon.c | 16 include/linux/hwmon.h | 27 +++ 2 files changed,

[PATCH v3 9/9] hwmon: (core) Add basic pwm attribute support to new API

Add basic pwm attribute support (no auto attributes) to new API. Reviewed-by: Jonathan Cameron Signed-off-by: Guenter Roeck --- v2: No change v2: Added patch Documentation/hwmon/hwmon-kernel-api.txt | 2 ++ drivers/hwmon/hwmon.c| 9

[PATCH v3 7/9] hwmon: (core) Add fan attribute support to new API

Acked-by: Punit Agrawal Reviewed-by: Jonathan Cameron Signed-off-by: Guenter Roeck --- v3: No change v2: No change drivers/hwmon/hwmon.c | 16 include/linux/hwmon.h | 27 +++ 2 files changed, 43 insertions(+) diff --git a/drivers/hwmon/hwmon.c

[PATCH v3 9/9] hwmon: (core) Add basic pwm attribute support to new API

Add basic pwm attribute support (no auto attributes) to new API. Reviewed-by: Jonathan Cameron Signed-off-by: Guenter Roeck --- v2: No change v2: Added patch Documentation/hwmon/hwmon-kernel-api.txt | 2 ++ drivers/hwmon/hwmon.c| 9 + include/linux/hwmon.h

[PATCH v3 6/9] hwmon: (core) Add energy and humidity attribute support to new API

Acked-by: Punit Agrawal Reviewed-by: Jonathan Cameron Signed-off-by: Guenter Roeck --- v3: No change drivers/hwmon/hwmon.c | 20 include/linux/hwmon.h | 29 + 2 files changed, 49

[PATCH v3 5/9] hwmon: (core) Add power attribute support to new API

Acked-by: Punit Agrawal Reviewed-by: Jonathan Cameron Signed-off-by: Guenter Roeck --- v3: No change v2: No change drivers/hwmon/hwmon.c | 30 include/linux/hwmon.h | 54

[PATCH v3 2/9] hwmon: (core) New hwmon registration API

Up to now, each hwmon driver has to implement its own sysfs attributes. This requires a lot of template code, and distracts from the driver's core function to read and write chip registers. To be able to reduce driver complexity, move sensor attribute handling and thermal zone registration into

[PATCH v3 0/9] hwmon: New hwmon registration API

Up to now, each hwmon driver has to implement its own sysfs attributes. This requires a lot of template code, and distracts from the driver's core function to read and write chip registers. To be able to reduce driver complexity, move sensor attribute handling and thermal zone registration into

[PATCH v3 6/9] hwmon: (core) Add energy and humidity attribute support to new API

Acked-by: Punit Agrawal Reviewed-by: Jonathan Cameron Signed-off-by: Guenter Roeck --- v3: No change drivers/hwmon/hwmon.c | 20 include/linux/hwmon.h | 29 + 2 files changed, 49 insertions(+) diff --git a/drivers/hwmon/hwmon.c

[PATCH v3 5/9] hwmon: (core) Add power attribute support to new API

Acked-by: Punit Agrawal Reviewed-by: Jonathan Cameron Signed-off-by: Guenter Roeck --- v3: No change v2: No change drivers/hwmon/hwmon.c | 30 include/linux/hwmon.h | 54 +++ 2 files changed, 84 insertions(+) diff

[PATCH v3 2/9] hwmon: (core) New hwmon registration API

Up to now, each hwmon driver has to implement its own sysfs attributes. This requires a lot of template code, and distracts from the driver's core function to read and write chip registers. To be able to reduce driver complexity, move sensor attribute handling and thermal zone registration into

[PATCH v3 0/9] hwmon: New hwmon registration API

Up to now, each hwmon driver has to implement its own sysfs attributes. This requires a lot of template code, and distracts from the driver's core function to read and write chip registers. To be able to reduce driver complexity, move sensor attribute handling and thermal zone registration into

[PATCH v3 4/9] hwmon: (core) Add current attribute support to new API

Acked-by: Punit Agrawal Reviewed-by: Jonathan Cameron Signed-off-by: Guenter Roeck --- v3: No change v2: No change drivers/hwmon/hwmon.c | 21 + include/linux/hwmon.h | 36 2

[PATCH v3 8/9] hwmon: (core) Document new kernel API

Describe the new registration API function as well as the data structures it requires. Acked-by: Punit Agrawal Reviewed-by: Jonathan Cameron Signed-off-by: Guenter Roeck --- v3: No change v2: Fixed typos

[PATCH v3 4/9] hwmon: (core) Add current attribute support to new API

Acked-by: Punit Agrawal Reviewed-by: Jonathan Cameron Signed-off-by: Guenter Roeck --- v3: No change v2: No change drivers/hwmon/hwmon.c | 21 + include/linux/hwmon.h | 36 2 files changed, 57 insertions(+) diff --git

[PATCH v3 8/9] hwmon: (core) Document new kernel API

Describe the new registration API function as well as the data structures it requires. Acked-by: Punit Agrawal Reviewed-by: Jonathan Cameron Signed-off-by: Guenter Roeck --- v3: No change v2: Fixed typos Documentation/hwmon/hwmon-kernel-api.txt | 229 ++- 1 file

  1   2   3   4   5   >