Re: [PATCH 4/9] drm/i915: Delete unnecessary braces in three functions

On Thu, 04 May 2017, SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 4 May 2017 13:40:53 +0200 > > Do not use curly brackets at some source code places > where a single statement should be sufficient. We only tend to do

Re: [PATCH 4/9] drm/i915: Delete unnecessary braces in three functions

On Thu, 04 May 2017, SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 4 May 2017 13:40:53 +0200 > > Do not use curly brackets at some source code places > where a single statement should be sufficient. We only tend to do this kind of changes when we're changing the surrounding code

Re: [PATCH 3/9] drm/i915: Replace 14 seq_printf() calls by seq_puts()

On Thu, 04 May 2017, Chris Wilson wrote: > On Thu, May 04, 2017 at 06:54:16PM +0200, SF Markus Elfring wrote: >> From: Markus Elfring >> Date: Thu, 4 May 2017 13:20:47 +0200 >> >> Some strings which did not contain data format

Re: [PATCH 3/9] drm/i915: Replace 14 seq_printf() calls by seq_puts()

On Thu, 04 May 2017, Chris Wilson wrote: > On Thu, May 04, 2017 at 06:54:16PM +0200, SF Markus Elfring wrote: >> From: Markus Elfring >> Date: Thu, 4 May 2017 13:20:47 +0200 >> >> Some strings which did not contain data format specifications should be put >> into a sequence. Thus use the

Re: [PATCH 6/9] drm/i915: Add spaces for better code readability

On Thu, 04 May 2017, SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 4 May 2017 14:04:38 +0200 > > Use space characters at some source code places according to > the Linux coding style convention. LGTM. Frankly the only

Re: [PATCH 6/9] drm/i915: Add spaces for better code readability

On Thu, 04 May 2017, SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 4 May 2017 14:04:38 +0200 > > Use space characters at some source code places according to > the Linux coding style convention. LGTM. Frankly the only concern I have with accepting this patch is that it encourages

Re: [PATCH 5/9] drm/i915: Adjust seven checks for null pointers

On Thu, 04 May 2017, SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 4 May 2017 13:52:19 +0200 > MIME-Version: 1.0 > Content-Type: text/plain; charset=UTF-8 > Content-Transfer-Encoding: 8bit > > The script “checkpatch.pl”

Re: [PATCH 5/9] drm/i915: Adjust seven checks for null pointers

On Thu, 04 May 2017, SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 4 May 2017 13:52:19 +0200 > MIME-Version: 1.0 > Content-Type: text/plain; charset=UTF-8 > Content-Transfer-Encoding: 8bit > > The script “checkpatch.pl” pointed information out like the following. > > Comparison to

RE: [PATCH v3] drivers:soc:fsl:qbman:qman.c: Sleep instead of stuck hacking jiffies.

Use msleep() instead of stucking with long delay will be more efficient. Signed-off-by: Karim Eshapa --- drivers/soc/fsl/qbman/qman.c | 6 +- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/drivers/soc/fsl/qbman/qman.c b/drivers/soc/fsl/qbman/qman.c

RE: [PATCH v3] drivers:soc:fsl:qbman:qman.c: Sleep instead of stuck hacking jiffies.

Use msleep() instead of stucking with long delay will be more efficient. Signed-off-by: Karim Eshapa --- drivers/soc/fsl/qbman/qman.c | 6 +- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/drivers/soc/fsl/qbman/qman.c b/drivers/soc/fsl/qbman/qman.c index 3d891db..18d391e

Re: [PATCH v8 1/5] x86: add simple udelay calibration

Hi, On 05/03/2017 06:38 AM, Boris Ostrovsky wrote: > On 03/21/2017 04:01 AM, Lu Baolu wrote: >> Add a simple udelay calibration in x86 architecture-specific >> boot-time initializations. This will get a workable estimate >> for loops_per_jiffy. Hence, udelay() could be used after this >>

Re: [PATCH v8 1/5] x86: add simple udelay calibration

Hi, On 05/03/2017 06:38 AM, Boris Ostrovsky wrote: > On 03/21/2017 04:01 AM, Lu Baolu wrote: >> Add a simple udelay calibration in x86 architecture-specific >> boot-time initializations. This will get a workable estimate >> for loops_per_jiffy. Hence, udelay() could be used after this >>

[PATCH v2] staging: lustre: cleanup le32 assignment to ldp_flags

Introduces a local var to collect flags and convert them to le32. Fixes the following sparse warnings: drivers/staging/lustre/lustre/lmv/lmv_obd.c:2305:23: warning: invalid assignment: |= drivers/staging/lustre/lustre/lmv/lmv_obd.c:2305:23:left side has type restricted __le32

[PATCH v2] staging: lustre: cleanup le32 assignment to ldp_flags

Introduces a local var to collect flags and convert them to le32. Fixes the following sparse warnings: drivers/staging/lustre/lustre/lmv/lmv_obd.c:2305:23: warning: invalid assignment: |= drivers/staging/lustre/lustre/lmv/lmv_obd.c:2305:23:left side has type restricted __le32

Question about SOCK_SEQPACKET

Hello, I have recently had occasion to use SOCK_SEQPACKET sockets on Linux, and noticed some odd behavior. When using sendmsg and recvmsg with these sockets, it seems that the "end-of-record" flag (MSG_EOR) is not being propagated correctly. The man page for recvmsg(2) states: > The msg_flags

Question about SOCK_SEQPACKET

Hello, I have recently had occasion to use SOCK_SEQPACKET sockets on Linux, and noticed some odd behavior. When using sendmsg and recvmsg with these sockets, it seems that the "end-of-record" flag (MSG_EOR) is not being propagated correctly. The man page for recvmsg(2) states: > The msg_flags

Re: [PATCH tip/sched/core v2] sched/rt: Simplify the IPI rt balancing logic

On Fri, 2017-05-05 at 06:26 +0200, Mike Galbraith wrote: > > To get rteval: > > > > $ git clone > > git://git.kernel.org/pub/scm/linux/kernel/git/clrkwllms/rteval.git > > $ cd rteval > > $ git checkout origin/v2/master > > ImportError: No module named ethtool > > Where does one find the

Re: [PATCH tip/sched/core v2] sched/rt: Simplify the IPI rt balancing logic

On Fri, 2017-05-05 at 06:26 +0200, Mike Galbraith wrote: > > To get rteval: > > > > $ git clone > > git://git.kernel.org/pub/scm/linux/kernel/git/clrkwllms/rteval.git > > $ cd rteval > > $ git checkout origin/v2/master > > ImportError: No module named ethtool > > Where does one find the

Re: [PATCH 3/3] of: fix sparse warnings in fdt, irq, and resolver code

On 05/04/17 11:00, Rob Herring wrote: > sparse generates the following warnings in drivers/of/: > > ../drivers/of/fdt.c:63:36: warning: cast to restricted __be32 > ../drivers/of/fdt.c:68:33: warning: cast to restricted __be32 > ../drivers/of/irq.c:105:88: warning: incorrect type in initializer

Re: [PATCH 3/3] of: fix sparse warnings in fdt, irq, and resolver code

On 05/04/17 11:00, Rob Herring wrote: > sparse generates the following warnings in drivers/of/: > > ../drivers/of/fdt.c:63:36: warning: cast to restricted __be32 > ../drivers/of/fdt.c:68:33: warning: cast to restricted __be32 > ../drivers/of/irq.c:105:88: warning: incorrect type in initializer

Re: [PATCH 2/3] of: fix sparse warning in of_pci_range_parser_one

On 05/04/17 11:00, Rob Herring wrote: > sparse gives the following warning for 'pci_space': > > ../drivers/of/address.c:266:26: warning: incorrect type in assignment > (different base types) > ../drivers/of/address.c:266:26:expected unsigned int [unsigned] > [usertype] pci_space >

Re: [PATCH 2/3] of: fix sparse warning in of_pci_range_parser_one

On 05/04/17 11:00, Rob Herring wrote: > sparse gives the following warning for 'pci_space': > > ../drivers/of/address.c:266:26: warning: incorrect type in assignment > (different base types) > ../drivers/of/address.c:266:26:expected unsigned int [unsigned] > [usertype] pci_space >

Re: [PATCH 1/3] of: fix sparse warnings in of_find_next_cache_node

On 05/04/17 11:00, Rob Herring wrote: > sparse gives a warning that 'handle' is not a __be32: > > ../drivers/of/base.c:2261:61: warning: incorrect type in argument 1 > (different base types) > ../drivers/of/base.c:2261:61:expected restricted __be32 const [usertype] > *p >

Re: [PATCH 1/3] of: fix sparse warnings in of_find_next_cache_node

On 05/04/17 11:00, Rob Herring wrote: > sparse gives a warning that 'handle' is not a __be32: > > ../drivers/of/base.c:2261:61: warning: incorrect type in argument 1 > (different base types) > ../drivers/of/base.c:2261:61:expected restricted __be32 const [usertype] > *p >

[rcu:dev.2017.05.02c 78/90] arch/arm/include/asm/irq.h:39:50: error: unknown type name 'cpumask_t'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2017.05.02c head: b69fe94f46adfa1b76504b0cd1b9604ea04db87d commit: 37b235df7033c20b00702b8aa30f7424fc0fb556 [78/90] rcu: Remove linux/cpumask.h from rcupdate.h config: arm-imx_v6_v7_defconfig (attached as

[rcu:dev.2017.05.02c 78/90] arch/arm/include/asm/irq.h:39:50: error: unknown type name 'cpumask_t'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2017.05.02c head: b69fe94f46adfa1b76504b0cd1b9604ea04db87d commit: 37b235df7033c20b00702b8aa30f7424fc0fb556 [78/90] rcu: Remove linux/cpumask.h from rcupdate.h config: arm-imx_v6_v7_defconfig (attached as

Re: [PATCH v3] x86/amd: don't set X86_BUG_SYSRET_SS_ATTRS when running under Xen

Any comments? Juergen On 27/04/17 07:01, Juergen Gross wrote: > When running as Xen pv guest X86_BUG_SYSRET_SS_ATTRS must not be set > on AMD cpus. > > This bug/feature bit is kind of special as it will be used very early > when switching threads. Setting the bit and clearing it a little bit >

Re: [PATCH v3] x86/amd: don't set X86_BUG_SYSRET_SS_ATTRS when running under Xen

Any comments? Juergen On 27/04/17 07:01, Juergen Gross wrote: > When running as Xen pv guest X86_BUG_SYSRET_SS_ATTRS must not be set > on AMD cpus. > > This bug/feature bit is kind of special as it will be used very early > when switching threads. Setting the bit and clearing it a little bit >

[PATCH 1/1] selftests: sync: add config fragment for testing sync framework

Unless the software synchronization objects (CONFIG_SW_SYNC) is enabled, the sync test will fail: Additional Information: Running tests in sync [RUN] Testing sync framework [RUN] Executing test_alloc_timeline [ERROR] Failure allocating timeline [RUN]

[PATCH 1/1] selftests: sync: add config fragment for testing sync framework

Unless the software synchronization objects (CONFIG_SW_SYNC) is enabled, the sync test will fail: Additional Information: Running tests in sync [RUN] Testing sync framework [RUN] Executing test_alloc_timeline [ERROR] Failure allocating timeline [RUN]

Re: [PATCH 7/9] drm/i915: Combine substrings for a message in gen6_drpc_info()

On Thu, May 04, 2017 at 09:12:32PM +0100, Chris Wilson wrote: > On Thu, May 04, 2017 at 06:59:23PM +0200, SF Markus Elfring wrote: > > From: Markus Elfring > > Date: Thu, 4 May 2017 14:15:00 +0200 > > > > The script "checkpatch.pl" pointed information out like the

Re: [PATCH 7/9] drm/i915: Combine substrings for a message in gen6_drpc_info()

On Thu, May 04, 2017 at 09:12:32PM +0100, Chris Wilson wrote: > On Thu, May 04, 2017 at 06:59:23PM +0200, SF Markus Elfring wrote: > > From: Markus Elfring > > Date: Thu, 4 May 2017 14:15:00 +0200 > > > > The script "checkpatch.pl" pointed information out like the following. > > > > WARNING:

Re: [PATCH 2/2] xen/input: add multi-touch support

Hi, Dmitry! On 04/21/2017 09:40 AM, Oleksandr Andrushchenko wrote: Hi, Dmitry! On 04/21/2017 05:10 AM, Dmitry Torokhov wrote: Hi Oleksandr, On Thu, Apr 13, 2017 at 02:38:04PM +0300, Oleksandr Andrushchenko wrote: From: Oleksandr Andrushchenko Extend

Re: [PATCH 2/2] xen/input: add multi-touch support

Hi, Dmitry! On 04/21/2017 09:40 AM, Oleksandr Andrushchenko wrote: Hi, Dmitry! On 04/21/2017 05:10 AM, Dmitry Torokhov wrote: Hi Oleksandr, On Thu, Apr 13, 2017 at 02:38:04PM +0300, Oleksandr Andrushchenko wrote: From: Oleksandr Andrushchenko Extend xen_kbdfront to provide multi-touch

Re: [PATCH 1/2] xen/input: use string constants from PV protocol

Hello, Dmitry! On 04/21/2017 09:42 AM, Oleksandr Andrushchenko wrote: On 04/21/2017 05:11 AM, Dmitry Torokhov wrote: On Thu, Apr 13, 2017 at 02:38:03PM +0300, Oleksandr Andrushchenko wrote: From: Oleksandr Andrushchenko Xen input para-virtual protocol

Re: new ...at() flag: AT_NO_JUMPS

On Thu, May 4, 2017 at 9:39 PM, Al Viro wrote: > On Thu, May 04, 2017 at 08:46:49PM -0700, Linus Torvalds wrote: >> On Thu, May 4, 2017 at 7:47 PM, Jann Horn wrote: >> > >> > Thread 1 starts an AT_BENEATH path walk using an O_PATH fd >> > pointing to

Re: [PATCH 1/2] xen/input: use string constants from PV protocol

Hello, Dmitry! On 04/21/2017 09:42 AM, Oleksandr Andrushchenko wrote: On 04/21/2017 05:11 AM, Dmitry Torokhov wrote: On Thu, Apr 13, 2017 at 02:38:03PM +0300, Oleksandr Andrushchenko wrote: From: Oleksandr Andrushchenko Xen input para-virtual protocol defines string constants used by both

Re: new ...at() flag: AT_NO_JUMPS

On Thu, May 4, 2017 at 9:39 PM, Al Viro wrote: > On Thu, May 04, 2017 at 08:46:49PM -0700, Linus Torvalds wrote: >> On Thu, May 4, 2017 at 7:47 PM, Jann Horn wrote: >> > >> > Thread 1 starts an AT_BENEATH path walk using an O_PATH fd >> > pointing to /srv/www/example.org/foo; the path given to

[PATCH] Staging: rtl8712: ieee80211: fixed brace coding style issue

Fixed coding style issue Signed-off-by: Jaya Durga --- drivers/staging/rtl8712/ieee80211.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/staging/rtl8712/ieee80211.c b/drivers/staging/rtl8712/ieee80211.c index d84da2b..512bf16 100644 ---

[PATCH] Staging: rtl8712: ieee80211: fixed brace coding style issue

Fixed coding style issue Signed-off-by: Jaya Durga --- drivers/staging/rtl8712/ieee80211.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/staging/rtl8712/ieee80211.c b/drivers/staging/rtl8712/ieee80211.c index d84da2b..512bf16 100644 ---

Re: new ...at() flag: AT_NO_JUMPS

On Thu, May 04, 2017 at 08:46:49PM -0700, Linus Torvalds wrote: > On Thu, May 4, 2017 at 7:47 PM, Jann Horn wrote: > > > > Thread 1 starts an AT_BENEATH path walk using an O_PATH fd > > pointing to /srv/www/example.org/foo; the path given to the syscall is > >

Re: new ...at() flag: AT_NO_JUMPS

On Thu, May 04, 2017 at 08:46:49PM -0700, Linus Torvalds wrote: > On Thu, May 4, 2017 at 7:47 PM, Jann Horn wrote: > > > > Thread 1 starts an AT_BENEATH path walk using an O_PATH fd > > pointing to /srv/www/example.org/foo; the path given to the syscall is > > "bar/../../../../etc/passwd". The

Re: new ...at() flag: AT_NO_JUMPS

On Thu, May 4, 2017 at 9:01 PM, Linus Torvalds wrote: > On Thu, May 4, 2017 at 8:00 PM, Al Viro wrote: >>> >>> That could still allow crossing mount-points, but only if they are >>> non-bind mounts and cannot let us escape. >>> >>> I'm not

Re: new ...at() flag: AT_NO_JUMPS

On Thu, May 4, 2017 at 9:01 PM, Linus Torvalds wrote: > On Thu, May 4, 2017 at 8:00 PM, Al Viro wrote: >>> >>> That could still allow crossing mount-points, but only if they are >>> non-bind mounts and cannot let us escape. >>> >>> I'm not sure if that's testable, though. >> >> This one isn't,

Re: [PATCH tip/sched/core v2] sched/rt: Simplify the IPI rt balancing logic

> To get rteval: > > $ git clone > git://git.kernel.org/pub/scm/linux/kernel/git/clrkwllms/rteval.git > $ cd rteval > $ git checkout origin/v2/master ImportError: No module named ethtool Where does one find the ethtool bits it seems to depend upon? -Mike

Re: [PATCH tip/sched/core v2] sched/rt: Simplify the IPI rt balancing logic

> To get rteval: > > $ git clone > git://git.kernel.org/pub/scm/linux/kernel/git/clrkwllms/rteval.git > $ cd rteval > $ git checkout origin/v2/master ImportError: No module named ethtool Where does one find the ethtool bits it seems to depend upon? -Mike

linux-next: Tree for May 5

Hi all, Please do not add any v4.13 destined material in your linux-next included branches until after v4.12-rc1 has been released. Changes since 20170504: The rdma tree gained a conflict against the pci tree. The spi-nor tree lost its build failure. Non-merge commits (relative to Linus' tree

linux-next: Tree for May 5

Hi all, Please do not add any v4.13 destined material in your linux-next included branches until after v4.12-rc1 has been released. Changes since 20170504: The rdma tree gained a conflict against the pci tree. The spi-nor tree lost its build failure. Non-merge commits (relative to Linus' tree

Re: [PATCH v7] Input: psxpad-spi - Add PlayStation 1/2 joypads via SPI interface Driver

Mr.Torokhov Mr.Herrmann > Anyway, I'd suggest leaving the patch unchanged. You can do the > modification as a follow-up. It is not urgent. I don't change now. Please continue with the processing. Regard. --- Tomohiro 2017-05-05 0:09 GMT+09:00 Tomohiro Yoshidomi : >

Re: [PATCH v7] Input: psxpad-spi - Add PlayStation 1/2 joypads via SPI interface Driver

Mr.Torokhov Mr.Herrmann > Anyway, I'd suggest leaving the patch unchanged. You can do the > modification as a follow-up. It is not urgent. I don't change now. Please continue with the processing. Regard. --- Tomohiro 2017-05-05 0:09 GMT+09:00 Tomohiro Yoshidomi : > Mr.Torokhov > Mr.Herrmann

Re: [linux-next][bisected 1945bc45] build brakes for PowerPC BE configuration on LPAR

On Thu, 2017-05-04 at 20:41 +1000, Nicholas Piggin wrote: > On Thu, 04 May 2017 14:54:19 +0530 > Abdul Haleem wrote: > > > Hi, > > > > linux-next build fails on BE config with next-20170424 onwards > > > > the patch https://lkml.org/lkml/2017/4/20/994 fixes a

Re: [linux-next][bisected 1945bc45] build brakes for PowerPC BE configuration on LPAR

On Thu, 2017-05-04 at 20:41 +1000, Nicholas Piggin wrote: > On Thu, 04 May 2017 14:54:19 +0530 > Abdul Haleem wrote: > > > Hi, > > > > linux-next build fails on BE config with next-20170424 onwards > > > > the patch https://lkml.org/lkml/2017/4/20/994 fixes a similar issue > > with kvm guest

Re: [PATCHv4 3/3] drm/vgem: Enable dmabuf import interfaces

On Thu, 2017-05-04 at 21:25 +0100, Chris Wilson wrote: > On Thu, May 04, 2017 at 11:45:48AM -0700, Laura Abbott wrote: > > > > Enable the GEM dma-buf import interfaces in addition to the export > > interfaces. This lets vgem be used as a test source for other allocators > > (e.g. Ion). > > > >

Re: [PATCHv4 3/3] drm/vgem: Enable dmabuf import interfaces

On Thu, 2017-05-04 at 21:25 +0100, Chris Wilson wrote: > On Thu, May 04, 2017 at 11:45:48AM -0700, Laura Abbott wrote: > > > > Enable the GEM dma-buf import interfaces in addition to the export > > interfaces. This lets vgem be used as a test source for other allocators > > (e.g. Ion). > > > >

Re: new ...at() flag: AT_NO_JUMPS

On Thu, May 4, 2017 at 8:00 PM, Al Viro wrote: >> >> That could still allow crossing mount-points, but only if they are >> non-bind mounts and cannot let us escape. >> >> I'm not sure if that's testable, though. > > This one isn't, unfortunately - there is no difference

Re: new ...at() flag: AT_NO_JUMPS

On Thu, May 4, 2017 at 8:00 PM, Al Viro wrote: >> >> That could still allow crossing mount-points, but only if they are >> non-bind mounts and cannot let us escape. >> >> I'm not sure if that's testable, though. > > This one isn't, unfortunately - there is no difference between bind and >

Re: new ...at() flag: AT_NO_JUMPS

On Thu, May 4, 2017 at 7:47 PM, Jann Horn wrote: > > Thread 1 starts an AT_BENEATH path walk using an O_PATH fd > pointing to /srv/www/example.org/foo; the path given to the syscall is > "bar/../../../../etc/passwd". The path walk enters the "bar" directory. > Thread 2 moves

Re: new ...at() flag: AT_NO_JUMPS

On Thu, May 4, 2017 at 7:47 PM, Jann Horn wrote: > > Thread 1 starts an AT_BENEATH path walk using an O_PATH fd > pointing to /srv/www/example.org/foo; the path given to the syscall is > "bar/../../../../etc/passwd". The path walk enters the "bar" directory. > Thread 2 moves

Re: [linux-sunxi] Re: [PATCH v6 08/13] drm/sun4i: add support for Allwinner DE2 mixers

On Fri, May 5, 2017 at 12:52 AM, wrote: > 在 2017-05-04 21:05，Maxime Ripard 写道： >> >> On Thu, May 04, 2017 at 07:48:53PM +0800, Icenowy Zheng wrote: >>> >>> Allwinner have a new "Display Engine 2.0" in their new SoCs, which comes >>> with mixers to do graphic processing and feed

Re: [linux-sunxi] Re: [PATCH v6 08/13] drm/sun4i: add support for Allwinner DE2 mixers

On Fri, May 5, 2017 at 12:52 AM, wrote: > 在 2017-05-04 21:05，Maxime Ripard 写道： >> >> On Thu, May 04, 2017 at 07:48:53PM +0800, Icenowy Zheng wrote: >>> >>> Allwinner have a new "Display Engine 2.0" in their new SoCs, which comes >>> with mixers to do graphic processing and feed data to TCON,

Re: [linux-sunxi] [PATCH v2 01/10] arm: sunxi: add support for R40 SoC

On Thu, May 4, 2017 at 9:49 PM, Icenowy Zheng wrote: > From: Icenowy Zheng Do you want to update your author email address? > > Allwinner R40 is a new SoC, with Quad Core Cortex-A7 and peripherals > like A20. > > Add support for it. > > Signed-off-by: Icenowy

Re: [linux-sunxi] [PATCH v2 01/10] arm: sunxi: add support for R40 SoC

On Thu, May 4, 2017 at 9:49 PM, Icenowy Zheng wrote: > From: Icenowy Zheng Do you want to update your author email address? > > Allwinner R40 is a new SoC, with Quad Core Cortex-A7 and peripherals > like A20. > > Add support for it. > > Signed-off-by: Icenowy Zheng Same here. For the

Re: linux-next: manual merge of the rdma tree with the pci tree

On 5/4/2017 8:19 PM, Stephen Rothwell wrote: > Hi Doug, > > Today's linux-next merge of the rdma tree got a conflict in: > > drivers/infiniband/hw/hfi1/hfi.h > > between commit: > > 21c433a74b6b ("IB/hfi1: Use pcie_flr() instead of duplicating it") > > from the pci tree and commit: > >

Re: linux-next: manual merge of the rdma tree with the pci tree

On 5/4/2017 8:19 PM, Stephen Rothwell wrote: > Hi Doug, > > Today's linux-next merge of the rdma tree got a conflict in: > > drivers/infiniband/hw/hfi1/hfi.h > > between commit: > > 21c433a74b6b ("IB/hfi1: Use pcie_flr() instead of duplicating it") > > from the pci tree and commit: > >

Re: [PATCH] ion: hisilicon: check the right value after ion_heap_create

Hi Laura, On 2017/5/5 1:47, Laura Abbott wrote: > On 05/04/2017 07:45 AM, Yisheng Xie wrote: >> From: Yisheng Xie >> >> It should check ipdev->heaps[i] whether it is error or null instead of >> ipdev->heaps, after ion_heap_create() for ipdev->heaps[i]. >> >>

Re: [linux-sunxi] [PATCH v6 10/13] drm/sun4i: tcon: add support for V3s TCON

On Thu, May 4, 2017 at 7:48 PM, Icenowy Zheng wrote: > Allwinner V3s SoC features a TCON without channel 1. > > Add support for it. > > Signed-off-by: Icenowy Zheng Reviewed-by: Chen-Yu Tsai

Re: [PATCH] ion: hisilicon: check the right value after ion_heap_create

Hi Laura, On 2017/5/5 1:47, Laura Abbott wrote: > On 05/04/2017 07:45 AM, Yisheng Xie wrote: >> From: Yisheng Xie >> >> It should check ipdev->heaps[i] whether it is error or null instead of >> ipdev->heaps, after ion_heap_create() for ipdev->heaps[i]. >> >> Signed-off-by: Yisheng Xie >> --- >>

Re: [linux-sunxi] [PATCH v6 10/13] drm/sun4i: tcon: add support for V3s TCON

On Thu, May 4, 2017 at 7:48 PM, Icenowy Zheng wrote: > Allwinner V3s SoC features a TCON without channel 1. > > Add support for it. > > Signed-off-by: Icenowy Zheng Reviewed-by: Chen-Yu Tsai

Re: [linux-sunxi] [PATCH v6 11/13] ARM: dts: sun8i: add DE2 nodes for V3s SoC

On Thu, May 4, 2017 at 7:48 PM, Icenowy Zheng wrote: > Allwinner V3s SoC features a "Display Engine 2.0" with only one TCON > which have RGB LCD output. Please also mention that it only has one mixer. For the subject, you could just say "Add device nodes for the display

Re: [linux-sunxi] [PATCH v6 11/13] ARM: dts: sun8i: add DE2 nodes for V3s SoC

On Thu, May 4, 2017 at 7:48 PM, Icenowy Zheng wrote: > Allwinner V3s SoC features a "Display Engine 2.0" with only one TCON > which have RGB LCD output. Please also mention that it only has one mixer. For the subject, you could just say "Add device nodes for the display pipeline". > > Add

Re: [PATCH] RTC: Add functionality to read/write rtc scratch registers

On Friday 05 May 2017 04:08 AM, Alexandre Belloni wrote: > Hi, > > On 03/05/2017 at 11:39:34 +0530, Keerthy wrote: >> On Tuesday 18 April 2017 10:50 AM, Keerthy wrote: >>> From: Russ Dill >>> >>> Many RTCs provide scratch registers that are maintained so long as the RTC >>>

Re: [PATCH] RTC: Add functionality to read/write rtc scratch registers

On Friday 05 May 2017 04:08 AM, Alexandre Belloni wrote: > Hi, > > On 03/05/2017 at 11:39:34 +0530, Keerthy wrote: >> On Tuesday 18 April 2017 10:50 AM, Keerthy wrote: >>> From: Russ Dill >>> >>> Many RTCs provide scratch registers that are maintained so long as the RTC >>> has power. Provide

Re: [linux-sunxi] [PATCH v6 12/13] ARM: dts: sun8i: add pinmux for LCD pins of V3s SoC

On Thu, May 4, 2017 at 7:48 PM, Icenowy Zheng wrote: > Allwinner V3s SoC features a set of pins that have functionality of RGB > LCD, the pins are at different pin ban than other SoCs. > > Add pinctrl node for them. > > Signed-off-by: Icenowy Zheng > --- >

Re: [linux-sunxi] [PATCH v6 12/13] ARM: dts: sun8i: add pinmux for LCD pins of V3s SoC

On Thu, May 4, 2017 at 7:48 PM, Icenowy Zheng wrote: > Allwinner V3s SoC features a set of pins that have functionality of RGB > LCD, the pins are at different pin ban than other SoCs. > > Add pinctrl node for them. > > Signed-off-by: Icenowy Zheng > --- > arch/arm/boot/dts/sun8i-v3s.dtsi | 9

Re: [linux-sunxi] [PATCH v6 03/13] dt-bindings: add bindings for DE2 on V3s SoC

On Thu, May 4, 2017 at 7:48 PM, Icenowy Zheng wrote: > Allwinner V3s SoC have a display engine which have a different pipeline > with older SoCs. > > Add document for it (new compatibles and the new "mixer" part). > > Signed-off-by: Icenowy Zheng > Acked-by: Rob

Re: [linux-sunxi] [PATCH v6 03/13] dt-bindings: add bindings for DE2 on V3s SoC

On Thu, May 4, 2017 at 7:48 PM, Icenowy Zheng wrote: > Allwinner V3s SoC have a display engine which have a different pipeline > with older SoCs. > > Add document for it (new compatibles and the new "mixer" part). > > Signed-off-by: Icenowy Zheng > Acked-by: Rob Herring > --- > Changes in v4: >

[Patch v2] x86/build: require only gcc use -maccumulate-outgoing-args

Other compilers, like clang, treat unknown compiler flags as errors. Signed-off-by: Nick Desaulniers --- arch/x86/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/x86/Makefile b/arch/x86/Makefile index 4430dd489620..12757a252e6b

[Patch v2] x86/build: require only gcc use -maccumulate-outgoing-args

Other compilers, like clang, treat unknown compiler flags as errors. Signed-off-by: Nick Desaulniers --- arch/x86/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/x86/Makefile b/arch/x86/Makefile index 4430dd489620..12757a252e6b 100644 --- a/arch/x86/Makefile

Re: [linux-sunxi] [PATCH v6 07/13] drm/sun4i: add a Kconfig option for sun4i-backend

On Thu, May 4, 2017 at 7:48 PM, Icenowy Zheng wrote: > As sun4i-backend is now a dedicated module, add an Kconfig option for > it to make it optional, since some build may only use other engines. > > Signed-off-by: Icenowy Zheng > --- > Splited out patch. > >

Re: [linux-sunxi] [PATCH v6 07/13] drm/sun4i: add a Kconfig option for sun4i-backend

On Thu, May 4, 2017 at 7:48 PM, Icenowy Zheng wrote: > As sun4i-backend is now a dedicated module, add an Kconfig option for > it to make it optional, since some build may only use other engines. > > Signed-off-by: Icenowy Zheng > --- > Splited out patch. > > drivers/gpu/drm/sun4i/Kconfig | 10

Re: [linux-sunxi] [PATCH v6 06/13] drm/sun4i: add a dedicated module for sun4i-backend and sun4i-layer

On Thu, May 4, 2017 at 7:48 PM, Icenowy Zheng wrote: > Currently the direct call from CRTC code to layer code has disappeared, > instead the layer's init function is called via the backend's ops. > > Add a dedicated module for sun4i-backend and sun4i-layer, and drop the >

Re: [linux-sunxi] [PATCH v6 06/13] drm/sun4i: add a dedicated module for sun4i-backend and sun4i-layer

On Thu, May 4, 2017 at 7:48 PM, Icenowy Zheng wrote: > Currently the direct call from CRTC code to layer code has disappeared, > instead the layer's init function is called via the backend's ops. > > Add a dedicated module for sun4i-backend and sun4i-layer, and drop the > EXPORT_SYMBOL from

Re: [PATCH] perf report: Make --branch-history work without callgraphs(-g) option in perf record

SNIP - if (symbol_conf.use_callchain) { + if (symbol_conf.use_callchain && + !symbol_conf.show_branchflag_count) { ui__error("Selected -g or --branch-history but no " "callchain data.

Re: [PATCH] perf report: Make --branch-history work without callgraphs(-g) option in perf record

SNIP - if (symbol_conf.use_callchain) { + if (symbol_conf.use_callchain && + !symbol_conf.show_branchflag_count) { ui__error("Selected -g or --branch-history but no " "callchain data.

RE: [PATCH] ACPI: SPCR: Use access width to determine mmio usage

Hi, > From: Jon Mason [mailto:jon.ma...@broadcom.com] > Sent: Thursday, May 4, 2017 11:06 PM > Subject: [PATCH] ACPI: SPCR: Use access width to determine mmio usage > > The current SPCR code does not check the access width of the mmio, and > uses a default of 8bit register accesses. This

RE: [PATCH] ACPI: SPCR: Use access width to determine mmio usage

Hi, > From: Jon Mason [mailto:jon.ma...@broadcom.com] > Sent: Thursday, May 4, 2017 11:06 PM > Subject: [PATCH] ACPI: SPCR: Use access width to determine mmio usage > > The current SPCR code does not check the access width of the mmio, and > uses a default of 8bit register accesses. This

Re: [PATCH 04/16] fpga: intel: pcie: parse feature list and create platform device for features.

On Thu, May 04, 2017 at 10:13:41AM -0500, Li, Yi wrote: > hi Hao > > > On 3/30/2017 7:08 AM, Wu Hao wrote: > >From: Xiao Guangrong > > > >Device Featuer List structure creates a link list of feature headers > >within the MMIO space to provide an extensiable way

Re: [PATCH 04/16] fpga: intel: pcie: parse feature list and create platform device for features.

On Thu, May 04, 2017 at 10:13:41AM -0500, Li, Yi wrote: > hi Hao > > > On 3/30/2017 7:08 AM, Wu Hao wrote: > >From: Xiao Guangrong > > > >Device Featuer List structure creates a link list of feature headers > >within the MMIO space to provide an extensiable way of adding features. > > > >The

Re: [linux-sunxi] [PATCH 04/13] drm/sun4i: return only planes for layers created

On Thu, May 4, 2017 at 7:41 PM, Icenowy Zheng wrote: > As we are going to add support for the Allwinner DE2 Mixer in sun4i-drm > driver, we will finally have two types of layers. > > Each layer is bound to a drm_plane that is CRTC-specific, so we create > them when initializing

Re: [linux-sunxi] [PATCH 04/13] drm/sun4i: return only planes for layers created

On Thu, May 4, 2017 at 7:41 PM, Icenowy Zheng wrote: > As we are going to add support for the Allwinner DE2 Mixer in sun4i-drm > driver, we will finally have two types of layers. > > Each layer is bound to a drm_plane that is CRTC-specific, so we create > them when initializing CRTC (calling

Re: new ...at() flag: AT_NO_JUMPS

On Thu, May 04, 2017 at 06:27:10PM -0700, Linus Torvalds wrote: > As mentioned last time, at least for the git usage, even relative > symlinks are a no-no - not because they'd escape, but simply because > git wants to see the *unique* name, and resolve relative symlinks to > either the symlink,

Re: new ...at() flag: AT_NO_JUMPS

On Thu, May 04, 2017 at 06:27:10PM -0700, Linus Torvalds wrote: > As mentioned last time, at least for the git usage, even relative > symlinks are a no-no - not because they'd escape, but simply because > git wants to see the *unique* name, and resolve relative symlinks to > either the symlink,

Re: [linux-sunxi] [PATCH v6 05/13] drm/sun4i: abstract a engine type

On Thu, May 4, 2017 at 7:48 PM, Icenowy Zheng wrote: > As we are going to add support for the Allwinner DE2 engine in sun4i-drm > driver, we will finally have two types of display engines -- the DE1 > backend and the DE2 mixer. They both do some display blending and feed >

Re: [linux-sunxi] [PATCH v6 05/13] drm/sun4i: abstract a engine type

On Thu, May 4, 2017 at 7:48 PM, Icenowy Zheng wrote: > As we are going to add support for the Allwinner DE2 engine in sun4i-drm > driver, we will finally have two types of display engines -- the DE1 > backend and the DE2 mixer. They both do some display blending and feed > graphics data to TCON,

[GIT PULL] liblockdep for 4.12

Hi Ingo, Please pull fixes for liblockdep. === The following changes since commit a351e9b9fc24e982ec2f0e76379a49826036da12: Linux 4.11 (2017-04-30 19:47:48 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux.git liblockdep-fixes for

[GIT PULL] liblockdep for 4.12

Hi Ingo, Please pull fixes for liblockdep. === The following changes since commit a351e9b9fc24e982ec2f0e76379a49826036da12: Linux 4.11 (2017-04-30 19:47:48 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux.git liblockdep-fixes for

[PATCH] tcmu: Add fifo type waiter list support to avoid starvation

From: Xiubo Li The fifo type waiter list will hold the udevs who are waiting for the blocks from the data global pool. The unmap thread will try to feed the first udevs in waiter list, if the global free blocks available are not enough, it will stop traversing the

[PATCH] tcmu: Add fifo type waiter list support to avoid starvation

From: Xiubo Li The fifo type waiter list will hold the udevs who are waiting for the blocks from the data global pool. The unmap thread will try to feed the first udevs in waiter list, if the global free blocks available are not enough, it will stop traversing the list and abort waking up the

Re: new ...at() flag: AT_NO_JUMPS

+CC drysdale in case he has thoughts on this On Fri, May 5, 2017 at 2:30 AM, Al Viro wrote: > On Mon, May 01, 2017 at 07:36:52PM +0200, Jann Horn wrote: > >> Oh, nice! >> >> It looks like this is somewhat similar to the old O_BENEATH proposal, >> but because the

Re: new ...at() flag: AT_NO_JUMPS

+CC drysdale in case he has thoughts on this On Fri, May 5, 2017 at 2:30 AM, Al Viro wrote: > On Mon, May 01, 2017 at 07:36:52PM +0200, Jann Horn wrote: > >> Oh, nice! >> >> It looks like this is somewhat similar to the old O_BENEATH proposal, >> but because the intentions behind the proposals

  1   2   3   4   5   6   7   8   9   10   >