[PATCH] mfd: cros_ec: Add missing free_irq in cros_ec_remove

Signed-off-by: Jeffy Chen --- drivers/mfd/cros_ec.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/mfd/cros_ec.c b/drivers/mfd/cros_ec.c index e31ac60..dc6ce90 100644 --- a/drivers/mfd/cros_ec.c +++ b/drivers/mfd/cros_ec.c @@ -183,6 +183,9 @@ int

[PATCH] mfd: cros_ec: Add missing free_irq in cros_ec_remove

Signed-off-by: Jeffy Chen --- drivers/mfd/cros_ec.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/mfd/cros_ec.c b/drivers/mfd/cros_ec.c index e31ac60..dc6ce90 100644 --- a/drivers/mfd/cros_ec.c +++ b/drivers/mfd/cros_ec.c @@ -183,6 +183,9 @@ int cros_ec_remove(struct

[PATCH v2] drm/sun4i: hdmi: Implement I2C adapter for A10s DDC bus

The drm_get_edid function should be used instead of drm_do_get_edid by exposing the DDC bus as an I2C adapter. Implement this for A10s. Signed-off-by: Jonathan Liu --- Changes for v2: - Rebased against Maxime's sunxi-drm/for-next branch - Fix up error paths in sun4i_hdmi_bind

[PATCH v2] drm/sun4i: hdmi: Implement I2C adapter for A10s DDC bus

The drm_get_edid function should be used instead of drm_do_get_edid by exposing the DDC bus as an I2C adapter. Implement this for A10s. Signed-off-by: Jonathan Liu --- Changes for v2: - Rebased against Maxime's sunxi-drm/for-next branch - Fix up error paths in sun4i_hdmi_bind so that the I2C

Re: [PATCH] drm/sun4i: hdmi: Implement I2C adapter for A10s DDC bus

Hi Chen-Yu, On 12 June 2017 at 13:28, Chen-Yu Tsai wrote: > On Mon, Jun 12, 2017 at 10:12 AM, Jonathan Liu wrote: >> The drm_get_edid function should be used instead of drm_do_get_edid by >> exposing the DDC bus as an I2C adapter. Implement this for A10s. > >

Re: [PATCH] drm/sun4i: hdmi: Implement I2C adapter for A10s DDC bus

Hi Chen-Yu, On 12 June 2017 at 13:28, Chen-Yu Tsai wrote: > On Mon, Jun 12, 2017 at 10:12 AM, Jonathan Liu wrote: >> The drm_get_edid function should be used instead of drm_do_get_edid by >> exposing the DDC bus as an I2C adapter. Implement this for A10s. > > Nice! It is my first Linux kernel

RE: [REGRESSION] Touchpad failure after e7348396c6d5 ("Input: ALPS - fix V8+ protocol handling (73 03 28)")

Hi, Laura, Could you try to check below modification? https://bugzilla.kernel.org/show_bug.cgi?id=195215#c10 This thread person said, the issue was fixed by this change. I guess it's a XY coordinate setting problem, though the code that before the patch is applied also has a problem. Best

RE: [REGRESSION] Touchpad failure after e7348396c6d5 ("Input: ALPS - fix V8+ protocol handling (73 03 28)")

Hi, Laura, Could you try to check below modification? https://bugzilla.kernel.org/show_bug.cgi?id=195215#c10 This thread person said, the issue was fixed by this change. I guess it's a XY coordinate setting problem, though the code that before the patch is applied also has a problem. Best

Re: [LKP] [lkp-robot] [EDAC, sb_edac] e2f747b1f4: kmsg.EDAC_sbridge:Failed_to_register_device_with_error

On 06/12, Ye Xiaolong wrote: >On 06/10, Zhuo, Qiuxu wrote: >>> From: Borislav Petkov [mailto:b...@alien8.de] >>> >>> Xiaolong, >>> >>> can you please run Qiuxu's patch to verify it fixes your issue? >> >> >>Hi Boris, >>I manually verified the fix patch on the Broadwell-DE server on which the

Re: [LKP] [lkp-robot] [EDAC, sb_edac] e2f747b1f4: kmsg.EDAC_sbridge:Failed_to_register_device_with_error

On 06/12, Ye Xiaolong wrote: >On 06/10, Zhuo, Qiuxu wrote: >>> From: Borislav Petkov [mailto:b...@alien8.de] >>> >>> Xiaolong, >>> >>> can you please run Qiuxu's patch to verify it fixes your issue? >> >> >>Hi Boris, >>I manually verified the fix patch on the Broadwell-DE server on which the

[RFC 5/7] zram: identify asynchronous IO's return value

For upcoming asynchronous IO like writeback, zram_rw_page should be aware of that whether requested IO was completed or submitted successfully, otherwise error. For the goal, zram_bvec_rw has three return values. -errno: returns error number 0: IO request is done synchronously 1: IO

[RFC 4/7] zram: add free space management in backing device

With backing device, zram needs management of free space of backing device. This patch adds bitmap logic to manage free space which is very naive. However, it would be simple enough as considering uncompressible pages's frequenty in zram. Signed-off-by: Minchan Kim ---

[RFC 5/7] zram: identify asynchronous IO's return value

For upcoming asynchronous IO like writeback, zram_rw_page should be aware of that whether requested IO was completed or submitted successfully, otherwise error. For the goal, zram_bvec_rw has three return values. -errno: returns error number 0: IO request is done synchronously 1: IO

[RFC 4/7] zram: add free space management in backing device

With backing device, zram needs management of free space of backing device. This patch adds bitmap logic to manage free space which is very naive. However, it would be simple enough as considering uncompressible pages's frequenty in zram. Signed-off-by: Minchan Kim ---

[RFC 0/7] writeback incompressible pages to storage

zRam is useful for memory saving with compressible pages but sometime, workload can be changed and system has lots of incompressible pages which is very harmful for zram. This patch supports writeback feature of zram so admin can set up a block device and with it, zram can save the memory via

[RFC 0/7] writeback incompressible pages to storage

zRam is useful for memory saving with compressible pages but sometime, workload can be changed and system has lots of incompressible pages which is very harmful for zram. This patch supports writeback feature of zram so admin can set up a block device and with it, zram can save the memory via

[RFC 1/7] zram: inlining zram_compress

zram_compress does several things, compress, entry alloc and check limitation. I did for just readbility but it hurts modulization.:( So this patch removes zram_compress functions and inline it in __zram_bvec_write for upcoming patches. Signed-off-by: Minchan Kim ---

[RFC 1/7] zram: inlining zram_compress

zram_compress does several things, compress, entry alloc and check limitation. I did for just readbility but it hurts modulization.:( So this patch removes zram_compress functions and inline it in __zram_bvec_write for upcoming patches. Signed-off-by: Minchan Kim ---

Re: [PATCH 0/6] Constant Time Memory Comparisons Are Important

On Mon, Jun 12, 2017 at 12:30 AM, Emil Lenngren wrote: > 2017-06-11 22:48 GMT+02:00 Emmanuel Grumbach : >> On Sun, Jun 11, 2017 at 4:36 PM, Kees Cook wrote: >>> >>> On Sun, Jun 11, 2017 at 1:13 AM, Kalle Valo

Re: [PATCH 0/6] Constant Time Memory Comparisons Are Important

On Mon, Jun 12, 2017 at 12:30 AM, Emil Lenngren wrote: > 2017-06-11 22:48 GMT+02:00 Emmanuel Grumbach : >> On Sun, Jun 11, 2017 at 4:36 PM, Kees Cook wrote: >>> >>> On Sun, Jun 11, 2017 at 1:13 AM, Kalle Valo wrote: >>> > "Jason A. Donenfeld" writes: >>> > >>> >> Whenever you're comparing two

[RFC 6/7] zram: write incompressible pages to backing device

This patch enables write IO to transfer data to backing device. For that, it implements write_to_bdev function which creates new bio and chaining with parent bio to make the parent bio asynchrnous. For rw_page which don't have parent bio, it submit owned bio and handle IO completion by

[RFC 3/7] zram: add interface to specify backing device

For writeback feature, user should set up backing device before the zram working. This patch enables the interface via /sys/block/zramX/backing_dev. Currently, it supports block device only but it could be enhanced for file as well. Signed-off-by: Minchan Kim ---

Re: [PATCH] fs: fcntl, avoid undefined behaviour

On 2016/10/14 17:23, Jiri Slaby wrote: > fcntl(0, F_SETOWN, 0x8000) triggers: > UBSAN: Undefined behaviour in fs/fcntl.c:118:7 > negation of -2147483648 cannot be represented in type 'int': > CPU: 1 PID: 18261 Comm: syz-executor Not tainted 4.8.1-0-syzkaller #1 > ... > Call Trace: > ... > []

[RFC 6/7] zram: write incompressible pages to backing device

This patch enables write IO to transfer data to backing device. For that, it implements write_to_bdev function which creates new bio and chaining with parent bio to make the parent bio asynchrnous. For rw_page which don't have parent bio, it submit owned bio and handle IO completion by

[RFC 3/7] zram: add interface to specify backing device

For writeback feature, user should set up backing device before the zram working. This patch enables the interface via /sys/block/zramX/backing_dev. Currently, it supports block device only but it could be enhanced for file as well. Signed-off-by: Minchan Kim --- drivers/block/zram/zram_drv.c

Re: [PATCH] fs: fcntl, avoid undefined behaviour

On 2016/10/14 17:23, Jiri Slaby wrote: > fcntl(0, F_SETOWN, 0x8000) triggers: > UBSAN: Undefined behaviour in fs/fcntl.c:118:7 > negation of -2147483648 cannot be represented in type 'int': > CPU: 1 PID: 18261 Comm: syz-executor Not tainted 4.8.1-0-syzkaller #1 > ... > Call Trace: > ... > []

[RFC 7/7] zram: read page from backing device

This patch enables read IO from backing device. For the feature, it implements two IO read functions to transfer data from backing storage. One is asynchronous IO function and other is synchronous one. A reason I need synchrnous IO is due to partial write which need to complete read IO before

[RFC 7/7] zram: read page from backing device

This patch enables read IO from backing device. For the feature, it implements two IO read functions to transfer data from backing storage. One is asynchronous IO function and other is synchronous one. A reason I need synchrnous IO is due to partial write which need to complete read IO before

[RFC 2/7] zram: rename zram_decompress_page with __zram_bvec_read

zram_decompress_page naming is not proper because it doesn't decompress if page was dedup hit or stored with compression. Use more abstract term and consistent with write path function __zram_bvec_write. Signed-off-by: Minchan Kim --- drivers/block/zram/zram_drv.c | 6

[RFC 2/7] zram: rename zram_decompress_page with __zram_bvec_read

zram_decompress_page naming is not proper because it doesn't decompress if page was dedup hit or stored with compression. Use more abstract term and consistent with write path function __zram_bvec_write. Signed-off-by: Minchan Kim --- drivers/block/zram/zram_drv.c | 6 +++--- 1 file changed, 3

Re: [PATCH] mm, memory_hotplug: support movable_node for hotplugable nodes

On Thu, Jun 08, 2017 at 02:23:18PM +0200, Michal Hocko wrote: >From: Michal Hocko > >movable_node kernel parameter allows to make hotplugable NUMA >nodes to put all the hotplugable memory into movable zone which >allows more or less reliable memory hotremove. At least this >is

Re: [PATCH] mm, memory_hotplug: support movable_node for hotplugable nodes

On Thu, Jun 08, 2017 at 02:23:18PM +0200, Michal Hocko wrote: >From: Michal Hocko > >movable_node kernel parameter allows to make hotplugable NUMA >nodes to put all the hotplugable memory into movable zone which >allows more or less reliable memory hotremove. At least this >is the case for the

Quick Loans

Apply for a loan at 3% reply to this Email for more Info

Quick Loans

Apply for a loan at 3% reply to this Email for more Info

Re: [PATCH 1/3] mm: add vm_insert_mixed_mkwrite()

On Fri, Jun 09, 2017 at 08:35:08PM -0700, Dan Williams wrote: > On Fri, Jun 9, 2017 at 8:03 PM, Ross Zwisler > wrote: > > And vm_insert_mixed_mkwrite() and vm_insert_mixed() are redundant with only > > the insert_pfn() line differing? This doesn't seem

Re: [PATCH 1/3] mm: add vm_insert_mixed_mkwrite()

On Fri, Jun 09, 2017 at 08:35:08PM -0700, Dan Williams wrote: > On Fri, Jun 9, 2017 at 8:03 PM, Ross Zwisler > wrote: > > And vm_insert_mixed_mkwrite() and vm_insert_mixed() are redundant with only > > the insert_pfn() line differing? This doesn't seem better...unless I'm > > missing something?

Re: [PATCH 2/3] cpufreq: schedutil: Fix selection algorithm while reducing frequency

On 10-06-17, 23:21, Joel Fernandes wrote: > On Sat, Jun 10, 2017 at 2:11 AM, Joel Fernandes wrote: > > On Fri, Jun 9, 2017 at 3:15 AM, Viresh Kumar > > wrote: > >> While reducing frequency if there are no frequencies available between > >> "current"

Re: [PATCH 2/3] cpufreq: schedutil: Fix selection algorithm while reducing frequency

On 10-06-17, 23:21, Joel Fernandes wrote: > On Sat, Jun 10, 2017 at 2:11 AM, Joel Fernandes wrote: > > On Fri, Jun 9, 2017 at 3:15 AM, Viresh Kumar > > wrote: > >> While reducing frequency if there are no frequencies available between > >> "current" and "next" calculated frequency, then the

[PATCH] i2c: ismt: fix wrong device address when unmap the data buffer

From: Liwei Song Fix the following calltrace: kernel BUG at drivers/iommu/intel-iommu.c:3260! invalid opcode: [#5] PREEMPT SMP Hardware name: Intel Corp. Harcuvar/Server, BIOS HAVLCRB0.X64.0013.D39.1608311820 08/31/2016 task: 880175389950 ti: 880176bec000

[PATCH] i2c: ismt: fix wrong device address when unmap the data buffer

From: Liwei Song Fix the following calltrace: kernel BUG at drivers/iommu/intel-iommu.c:3260! invalid opcode: [#5] PREEMPT SMP Hardware name: Intel Corp. Harcuvar/Server, BIOS HAVLCRB0.X64.0013.D39.1608311820 08/31/2016 task: 880175389950 ti: 880176bec000 task.ti: 880176bec000

[PATCH] drm: panel: fix s6e3ha2.c build errors

From: Randy Dunlap Fix build errors in panel-samsung-s6e3ha2.c driver build. The driver uses backlight interfaces so it should depend on BACKLIGHT_CLASS_DEVICE. drivers/built-in.o: In function `s6e3ha2_remove': panel-samsung-s6e3ha2.c:(.text+0xe49c2): undefined reference

[PATCH] drm: panel: fix s6e3ha2.c build errors

From: Randy Dunlap Fix build errors in panel-samsung-s6e3ha2.c driver build. The driver uses backlight interfaces so it should depend on BACKLIGHT_CLASS_DEVICE. drivers/built-in.o: In function `s6e3ha2_remove': panel-samsung-s6e3ha2.c:(.text+0xe49c2): undefined reference to

Re: [PATCH 3/3] cpufreq: intel_pstate: Provide resolve_freq() to fix regression

On 10-06-17, 02:26, Joel Fernandes wrote: > On Fri, Jun 9, 2017 at 3:15 AM, Viresh Kumar wrote: > > When the schedutil governor calls cpufreq_driver_resolve_freq() for the > > intel_pstate (in passive mode) driver, it simply returns the requested > > frequency as there is

Re: [PATCH 3/3] cpufreq: intel_pstate: Provide resolve_freq() to fix regression

On 10-06-17, 02:26, Joel Fernandes wrote: > On Fri, Jun 9, 2017 at 3:15 AM, Viresh Kumar wrote: > > When the schedutil governor calls cpufreq_driver_resolve_freq() for the > > intel_pstate (in passive mode) driver, it simply returns the requested > > frequency as there is no ->resolve_freq()

Re: [PATCH] cpufreq: conservative: Allow down_threshold to take values from 1 to 10

On 11-06-17, 17:28, Tomasz Wilczyński wrote: > Commit 27ed3cd2ebf4cd78b198be9758c538cdede36d8a ("cpufreq: conservative: > Fix the logic in frequency decrease checking") removed the 10 point > substraction when comparing the load against down_threshold but did not > remove the related limit for the

Re: [PATCH] cpufreq: conservative: Allow down_threshold to take values from 1 to 10

On 11-06-17, 17:28, Tomasz Wilczyński wrote: > Commit 27ed3cd2ebf4cd78b198be9758c538cdede36d8a ("cpufreq: conservative: > Fix the logic in frequency decrease checking") removed the 10 point > substraction when comparing the load against down_threshold but did not > remove the related limit for the

[PATCH 23/27] unicore32: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

[PATCH 23/27] unicore32: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

[PATCH 21/27] sparc: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

[PATCH 21/27] sparc: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

[PATCH 03/27] kbuild: pass dst= to Makefile.headersinst from top Makefile

We can always pass dst= from the top Makefile. This will simplify the logic in Makefile.headersinst. Signed-off-by: Masahiro Yamada --- Makefile | 4 ++-- scripts/Makefile.headersinst | 7 ++- 2 files changed, 4 insertions(+), 7

[PATCH 03/27] kbuild: pass dst= to Makefile.headersinst from top Makefile

We can always pass dst= from the top Makefile. This will simplify the logic in Makefile.headersinst. Signed-off-by: Masahiro Yamada --- Makefile | 4 ++-- scripts/Makefile.headersinst | 7 ++- 2 files changed, 4 insertions(+), 7 deletions(-) diff --git a/Makefile

[PATCH 01/27] kbuild: remove useless $(gen) variable in Makefile.headersinst

We have no true case for the $(if $(gen), ...) conditional. Drop it to simplify the gendir calculation. Signed-off-by: Masahiro Yamada --- scripts/Makefile.headersinst | 5 + 1 file changed, 1 insertion(+), 4 deletions(-) diff --git

[PATCH 01/27] kbuild: remove useless $(gen) variable in Makefile.headersinst

We have no true case for the $(if $(gen), ...) conditional. Drop it to simplify the gendir calculation. Signed-off-by: Masahiro Yamada --- scripts/Makefile.headersinst | 5 + 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/scripts/Makefile.headersinst

[PATCH 13/27] m32r: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

[PATCH 13/27] m32r: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

[PATCH 02/27] kbuild: fix comment about dst of headers_{install,check}_all

Commit 61562f981e92 ("uapi: export all arch specifics directories") changed the dst from asm- to arch- for headers_install_all or headers_check_all. Update the comment. Signed-off-by: Masahiro Yamada --- Makefile | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH 25/27] kbuild: do not include old-kbuild-file from Makefile.headersinst

Now asm-generic wrappers to be exported are all listed in arch/*/include/uapi/asm/Kbuild. "make headers_install" no longer depends on any Kbuild files outside uapi directories. Signed-off-by: Masahiro Yamada --- scripts/Makefile.headersinst | 5 - 1 file

[PATCH 02/27] kbuild: fix comment about dst of headers_{install,check}_all

Commit 61562f981e92 ("uapi: export all arch specifics directories") changed the dst from asm- to arch- for headers_install_all or headers_check_all. Update the comment. Signed-off-by: Masahiro Yamada --- Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Makefile

[PATCH 25/27] kbuild: do not include old-kbuild-file from Makefile.headersinst

Now asm-generic wrappers to be exported are all listed in arch/*/include/uapi/asm/Kbuild. "make headers_install" no longer depends on any Kbuild files outside uapi directories. Signed-off-by: Masahiro Yamada --- scripts/Makefile.headersinst | 5 - 1 file changed, 5 deletions(-) diff

[PATCH 26/27] kbuild: split exported generic header creation into uapi-asm-generic

When we install headers, we are interested only in headers under uapi directories. Split out uapi-asm-generic target and make headers_install depend on it. It will avoid generating unneeded asm-generic wrappers. Signed-off-by: Masahiro Yamada --- Makefile | 7

[PATCH 26/27] kbuild: split exported generic header creation into uapi-asm-generic

When we install headers, we are interested only in headers under uapi directories. Split out uapi-asm-generic target and make headers_install depend on it. It will avoid generating unneeded asm-generic wrappers. Signed-off-by: Masahiro Yamada --- Makefile | 7 --- 1 file changed, 4

[PATCH 16/27] nios2: remove unneeded arch/nios2/include/(generated/)asm/signal.h

Currently, NIOS2 has three signal.h files under arch/nios2/include: [1] arch/nios2/include/asm/signal.h [2] arch/nios2/include/uapi/asm/signal.h [3] arch/nios2/include/generated/asm/signal.h [3] is build-time generated by scripts/Makefile.asm-generic. However,

[PATCH 27/27] kbuild: remove wrapper files handling from Makefile.headersinst

scripts/Makefike.headersinst creates asm-generic wrappers by itself because scripts/Makefile.asm-generic created some of exported wrappers outside uapi directories. Now this distortion has been fixed. scripts/Makefile.headersinst can simply copy wrappers created by scripts/Makefile.asm-generic.

[PATCH 17/27] nios2: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

[PATCH 16/27] nios2: remove unneeded arch/nios2/include/(generated/)asm/signal.h

Currently, NIOS2 has three signal.h files under arch/nios2/include: [1] arch/nios2/include/asm/signal.h [2] arch/nios2/include/uapi/asm/signal.h [3] arch/nios2/include/generated/asm/signal.h [3] is build-time generated by scripts/Makefile.asm-generic. However,

[PATCH 27/27] kbuild: remove wrapper files handling from Makefile.headersinst

scripts/Makefike.headersinst creates asm-generic wrappers by itself because scripts/Makefile.asm-generic created some of exported wrappers outside uapi directories. Now this distortion has been fixed. scripts/Makefile.headersinst can simply copy wrappers created by scripts/Makefile.asm-generic.

[PATCH 17/27] nios2: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

[PATCH 12/27] ia64: move generic-y of exported headers to uapi/asm/Kbuild

"generic-y += kvm_para.h" is doubled in asm/Kbuild and uapi/asm/Kbuild. The one in the former should be simply removed because kvm_para.h is exported. Signed-off-by: Masahiro Yamada --- arch/ia64/include/asm/Kbuild | 2 -- 1 file changed, 2 deletions(-) diff

[PATCH 00/27] kbuild, arch: complete UAPI de-coupling and cleanup scripts/Makefile.headersinst

In v4.12-rc1, we had a big progress for headers_install. All (and only) headers under UAPI directories are exported. However, asm-generic wrappers are still exceptions because most of arch/*/include/asm/Kbuild include "generic-y" for exported headers. As a result, many of generic-wrappers to be

[PATCH 22/27] tile: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

[PATCH 09/27] cris: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

[PATCH 12/27] ia64: move generic-y of exported headers to uapi/asm/Kbuild

"generic-y += kvm_para.h" is doubled in asm/Kbuild and uapi/asm/Kbuild. The one in the former should be simply removed because kvm_para.h is exported. Signed-off-by: Masahiro Yamada --- arch/ia64/include/asm/Kbuild | 2 -- 1 file changed, 2 deletions(-) diff --git

[PATCH 00/27] kbuild, arch: complete UAPI de-coupling and cleanup scripts/Makefile.headersinst

In v4.12-rc1, we had a big progress for headers_install. All (and only) headers under UAPI directories are exported. However, asm-generic wrappers are still exceptions because most of arch/*/include/asm/Kbuild include "generic-y" for exported headers. As a result, many of generic-wrappers to be

[PATCH 22/27] tile: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

[PATCH 09/27] cris: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

[PATCH 15/27] metag: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

[PATCH 15/27] metag: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

[PATCH 20/27] sh: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

[PATCH 08/27] c6x: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

[PATCH 20/27] sh: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

[PATCH 08/27] c6x: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

[PATCH 10/27] h8300: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

[PATCH 24/27] xtensa: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

[PATCH 10/27] h8300: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

[PATCH 24/27] xtensa: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

[PATCH 05/27] ARM: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

[PATCH 05/27] ARM: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

[PATCH 18/27] openrisc: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

Re: [PATCH] drm/sun4i: hdmi: Implement I2C adapter for A10s DDC bus

On Mon, Jun 12, 2017 at 10:12 AM, Jonathan Liu wrote: > The drm_get_edid function should be used instead of drm_do_get_edid by > exposing the DDC bus as an I2C adapter. Implement this for A10s. Nice! > > Signed-off-by: Jonathan Liu > --- >

[PATCH 18/27] openrisc: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

Re: [PATCH] drm/sun4i: hdmi: Implement I2C adapter for A10s DDC bus

On Mon, Jun 12, 2017 at 10:12 AM, Jonathan Liu wrote: > The drm_get_edid function should be used instead of drm_do_get_edid by > exposing the DDC bus as an I2C adapter. Implement this for A10s. Nice! > > Signed-off-by: Jonathan Liu > --- > drivers/gpu/drm/sun4i/Makefile | 1 + >

[PATCH 11/27] hexagon: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

[PATCH 07/27] blackfin: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

[PATCH 19/27] parisc: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

[PATCH 11/27] hexagon: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

[PATCH 07/27] blackfin: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

[PATCH 19/27] parisc: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

[PATCH 14/27] m68k: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

[PATCH 06/27] arc: move generic-y of exported headers to uapi/asm/Kbuild

Since commit fcc8487d477a ("uapi: export all headers under uapi directories"), all (and only) headers under uapi directories are exported, but asm-generic wrappers are still exceptions. scripts/Makefile.headersinst still need to deal with old-kbuild-file for headers listed in

  1   2   3   4   5   >