[PATCH 0/2] ALSA-Digigram VX222: Fine-tuning for four function implementations

From: Markus Elfring Date: Sat, 18 Nov 2017 21:27:50 +0100 Two update suggestions were taken into account from static source code analysis. Markus Elfring (2): Adjust ten function calls together with a variable assignment Use common error handling code in two

[PATCH 0/2] ALSA-Digigram VX222: Fine-tuning for four function implementations

From: Markus Elfring Date: Sat, 18 Nov 2017 21:27:50 +0100 Two update suggestions were taken into account from static source code analysis. Markus Elfring (2): Adjust ten function calls together with a variable assignment Use common error handling code in two functions

[PATCH] ARM: exynos: add machine description for ODROID-XU3/4

This patch is to add the machine descriptions for ODROID-XU3/4 boards in order to present the hardware name at /proc/cputinfo rather than "SAMSUNG EXYNOS (Flattened Device Tree)". An embedded open source project, such as DietPi, reads the hardware name to run different features. $ cat

[PATCH] ARM: exynos: add machine description for ODROID-XU3/4

This patch is to add the machine descriptions for ODROID-XU3/4 boards in order to present the hardware name at /proc/cputinfo rather than "SAMSUNG EXYNOS (Flattened Device Tree)". An embedded open source project, such as DietPi, reads the hardware name to run different features. $ cat

Re: [RFC v2] prctl: prctl(PR_SET_IDLE, PR_IDLE_MODE_KILLME), for stateless idle loops

On Fri, Nov 3, 2017 at 2:09 AM, Michal Hocko wrote: > On Thu 02-11-17 23:35:44, Shawn Landden wrote: >> 16 bytes per process is kinda spendy, but I want to keep >> lru behavior, which mem_score_adj does not allow. When a supervisor, >> like Android's user input is keeping track

Re: [RFC v2] prctl: prctl(PR_SET_IDLE, PR_IDLE_MODE_KILLME), for stateless idle loops

On Fri, Nov 3, 2017 at 2:09 AM, Michal Hocko wrote: > On Thu 02-11-17 23:35:44, Shawn Landden wrote: >> 16 bytes per process is kinda spendy, but I want to keep >> lru behavior, which mem_score_adj does not allow. When a supervisor, >> like Android's user input is keeping track this can be done

Re: [GIT PULL] platform-drivers-x86 for 4.15-1

On Sat, Nov 18, 2017 at 10:37 AM, Linus Torvalds wrote: > > So I note that you seem to use the same summary script that Darren used. .. oh, and I note a *much* worse issue. You add new drivers and then default them to "on". THAT IS COMPLETELY UNACCEPTABLE. I

Re: [GIT PULL] platform-drivers-x86 for 4.15-1

On Sat, Nov 18, 2017 at 10:37 AM, Linus Torvalds wrote: > > So I note that you seem to use the same summary script that Darren used. .. oh, and I note a *much* worse issue. You add new drivers and then default them to "on". THAT IS COMPLETELY UNACCEPTABLE. I don't know why I have to say this

seccomp() SECCOMP_RET_KILL_PROCESS text for man page

Hi Kees, I came up with the following text (patch below) to describe the SECCOMP_RET_KILL_PROCESS action that you added in 4.14. Does it look okay? SECCOMP_RET_KILL_PROCESS (since Linux 4.14) This value results in immediate termination of the process, with a

seccomp() SECCOMP_RET_KILL_PROCESS text for man page

Hi Kees, I came up with the following text (patch below) to describe the SECCOMP_RET_KILL_PROCESS action that you added in 4.14. Does it look okay? SECCOMP_RET_KILL_PROCESS (since Linux 4.14) This value results in immediate termination of the process, with a

Re: [PULL REQUEST] nfsd changes for 4.15

On Sat, Nov 18, 2017 at 10:40 AM, J. Bruce Fields wrote: > Please pull nfsd changes for 4.15 from: Hmm. This had a tracepoint conflict with the nfs client pull. The resolution seems obvious and I did it, but I'd like people to review the end result but particularly also

Re: [PULL REQUEST] nfsd changes for 4.15

On Sat, Nov 18, 2017 at 10:40 AM, J. Bruce Fields wrote: > Please pull nfsd changes for 4.15 from: Hmm. This had a tracepoint conflict with the nfs client pull. The resolution seems obvious and I did it, but I'd like people to review the end result but particularly also their workflows, because

Re: [PATCH] NFSv4: Ensure gcc 4.4.4 can compile initialiser for "invalid_stateid"

On 11/18/2017 01:50 PM, Trond Myklebust wrote: gcc 4.4.4 is too old to have full C11 anonymous union support, so the current initialiser fails to compile. Reported-by: Boris Ostrovsky Signed-off-by: Trond Myklebust

Re: [PATCH] NFSv4: Ensure gcc 4.4.4 can compile initialiser for "invalid_stateid"

On 11/18/2017 01:50 PM, Trond Myklebust wrote: gcc 4.4.4 is too old to have full C11 anonymous union support, so the current initialiser fails to compile. Reported-by: Boris Ostrovsky Signed-off-by: Trond Myklebust (compile-)Tested-by: Boris Ostrovsky --- fs/nfs/nfs4state.c | 4 ++--

Re: [PATCH 05/10] x86: jailhouse: Set up timekeeping

On 2017-11-17 23:49, Thomas Gleixner wrote: > On Thu, 16 Nov 2017, Jan Kiszka wrote: >> Calibrate the TSC and, where necessary, the APIC timer against the >> TMTIMER. We need our own implementation as neither the PIC nor the HPET >> are available, and the standard calibration routines try to make

Re: [PATCH 05/10] x86: jailhouse: Set up timekeeping

On 2017-11-17 23:49, Thomas Gleixner wrote: > On Thu, 16 Nov 2017, Jan Kiszka wrote: >> Calibrate the TSC and, where necessary, the APIC timer against the >> TMTIMER. We need our own implementation as neither the PIC nor the HPET >> are available, and the standard calibration routines try to make

Re: [PATCH 02/10] x86: jailhouse: Add infrastructure for running in non-root cell

On 2017-11-17 22:54, Thomas Gleixner wrote: > On Thu, 16 Nov 2017, Jan Kiszka wrote: > >> +config JAILHOUSE_GUEST >> +bool "Jailhouse non-root cell support" >> +depends on PARAVIRT && X86_64 >> +---help--- >> + This option allows to run Linux as guest in a Jailhouse non-root >>

Re: [PATCH 02/10] x86: jailhouse: Add infrastructure for running in non-root cell

On 2017-11-17 22:54, Thomas Gleixner wrote: > On Thu, 16 Nov 2017, Jan Kiszka wrote: > >> +config JAILHOUSE_GUEST >> +bool "Jailhouse non-root cell support" >> +depends on PARAVIRT && X86_64 >> +---help--- >> + This option allows to run Linux as guest in a Jailhouse non-root >>

Re: [patch V2 02/11] LICENSES: Add the GPL 2.0 license

>This is neither the GPL-2.0 from >https://www.gnu.org/licenses/gpl-2.0.txt I think it should be the copy from COPYING, in fact, since that's the exact GPL 2.0 license the kernel is under. Library GPL is factually correct; Lesser GPL is a newer name for the same license, but COPYING retains the

Re: [patch V2 02/11] LICENSES: Add the GPL 2.0 license

>This is neither the GPL-2.0 from >https://www.gnu.org/licenses/gpl-2.0.txt I think it should be the copy from COPYING, in fact, since that's the exact GPL 2.0 license the kernel is under. Library GPL is factually correct; Lesser GPL is a newer name for the same license, but COPYING retains the

Re: [patch V2 02/11] LICENSES: Add the GPL 2.0 license

You may be confusing things because of a newer version. On Sat, Nov 18, 2017 at 11:03 AM, Charlemagne Lasse wrote: > > That should be "GNU Lesser General Public" and not "GNU Library General > Public" That's just FSF revisionism. It used to be called "Library" over

[PATCH 3/3] ALSA: trident: Use common error handling code in snd_trident_mixer()

From: Markus Elfring Date: Sat, 18 Nov 2017 19:49:50 +0100 Adjust jump targets so that a bit of exception handling can be better reused at the end of this function. Signed-off-by: Markus Elfring --- sound/pci/trident/trident_main.c

Re: [patch V2 02/11] LICENSES: Add the GPL 2.0 license

You may be confusing things because of a newer version. On Sat, Nov 18, 2017 at 11:03 AM, Charlemagne Lasse wrote: > > That should be "GNU Lesser General Public" and not "GNU Library General > Public" That's just FSF revisionism. It used to be called "Library" over "Lesser", in the original

[PATCH 3/3] ALSA: trident: Use common error handling code in snd_trident_mixer()

From: Markus Elfring Date: Sat, 18 Nov 2017 19:49:50 +0100 Adjust jump targets so that a bit of exception handling can be better reused at the end of this function. Signed-off-by: Markus Elfring --- sound/pci/trident/trident_main.c | 71 +++- 1 file

[PATCH 2/3] ALSA: trident: Use common error handling code in two functions

From: Markus Elfring Date: Sat, 18 Nov 2017 19:29:35 +0100 Add jump targets so that a bit of exception handling can be better reused at the end of these functions. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring

[PATCH 2/3] ALSA: trident: Use common error handling code in two functions

From: Markus Elfring Date: Sat, 18 Nov 2017 19:29:35 +0100 Add jump targets so that a bit of exception handling can be better reused at the end of these functions. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- sound/pci/trident/trident.c |

[PATCH 1/3] ALSA: trident: Adjust 34 function calls together with a variable assignment

From: Markus Elfring Date: Sat, 18 Nov 2017 18:50:22 +0100 The script "checkpatch.pl" pointed information out like the following. ERROR: do not use assignment in if condition Thus fix affected source code places. Signed-off-by: Markus Elfring

[PATCH 1/3] ALSA: trident: Adjust 34 function calls together with a variable assignment

From: Markus Elfring Date: Sat, 18 Nov 2017 18:50:22 +0100 The script "checkpatch.pl" pointed information out like the following. ERROR: do not use assignment in if condition Thus fix affected source code places. Signed-off-by: Markus Elfring --- sound/pci/trident/trident.c | 24

[PATCH 0/3] ALSA-Trident 4DWave: Fine-tuning for nine function implementations

From: Markus Elfring Date: Sat, 18 Nov 2017 19:50:12 +0100 A few update suggestions were taken into account from static source code analysis. Markus Elfring (3): Adjust 34 function calls together with a variable assignment Use common error handling code in two

[PATCH 0/3] ALSA-Trident 4DWave: Fine-tuning for nine function implementations

From: Markus Elfring Date: Sat, 18 Nov 2017 19:50:12 +0100 A few update suggestions were taken into account from static source code analysis. Markus Elfring (3): Adjust 34 function calls together with a variable assignment Use common error handling code in two functions Use common error

Re: [patch V2 02/11] LICENSES: Add the GPL 2.0 license

2017-11-18 20:03 GMT+01:00 Charlemagne Lasse : >> +Ty Coon, President of Vice >> + >> +This General Public License does not permit incorporating your program into >> +proprietary programs. If your program is a subroutine library, you may >> +consider it more useful

Re: [patch V2 02/11] LICENSES: Add the GPL 2.0 license

2017-11-18 20:03 GMT+01:00 Charlemagne Lasse : >> +Ty Coon, President of Vice >> + >> +This General Public License does not permit incorporating your program into >> +proprietary programs. If your program is a subroutine library, you may >> +consider it more useful to permit linking

Re: [patch V2 02/11] LICENSES: Add the GPL 2.0 license

2017-11-16 19:33 GMT+01:00 Thomas Gleixner : > Add the full text of the GPL 2.0 license to the kernel tree. It was > copied directly from: > >https://spdx.org/licenses/GPL-2.0.html#licenseText > > Add the required tags for reference and tooling. > > Signed-off-by: Thomas

Re: [patch V2 02/11] LICENSES: Add the GPL 2.0 license

2017-11-16 19:33 GMT+01:00 Thomas Gleixner : > Add the full text of the GPL 2.0 license to the kernel tree. It was > copied directly from: > >https://spdx.org/licenses/GPL-2.0.html#licenseText > > Add the required tags for reference and tooling. > > Signed-off-by: Thomas Gleixner NACKed-by:

[PATCH] NFSv4: Ensure gcc 4.4.4 can compile initialiser for "invalid_stateid"

gcc 4.4.4 is too old to have full C11 anonymous union support, so the current initialiser fails to compile. Reported-by: Boris Ostrovsky Signed-off-by: Trond Myklebust --- fs/nfs/nfs4state.c | 4 ++-- 1 file changed, 2 insertions(+),

[PATCH] NFSv4: Ensure gcc 4.4.4 can compile initialiser for "invalid_stateid"

gcc 4.4.4 is too old to have full C11 anonymous union support, so the current initialiser fails to compile. Reported-by: Boris Ostrovsky Signed-off-by: Trond Myklebust --- fs/nfs/nfs4state.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fs/nfs/nfs4state.c

Re: [PATCH v2 net-next] net/tcp: trace all TCP/IP state transition with tcp_set_state tracepoint

> On Nov 18, 2017, at 7:32 AM, Yafang Shao wrote: > > The TCP/IP transition from TCP_LISTEN to TCP_SYN_RECV and some other > transitions are not traced with tcp_set_state tracepoint. > > In order to trace the whole tcp lifespans, two helpers are introduced, > void

Re: [PATCH v2 net-next] net/tcp: trace all TCP/IP state transition with tcp_set_state tracepoint

> On Nov 18, 2017, at 7:32 AM, Yafang Shao wrote: > > The TCP/IP transition from TCP_LISTEN to TCP_SYN_RECV and some other > transitions are not traced with tcp_set_state tracepoint. > > In order to trace the whole tcp lifespans, two helpers are introduced, > void __tcp_set_state(struct sock

Re: Cannot boot with rootfs from eMMC if maxcpus=1

On 11/09/2017 08:14 AM, Richard Schmitt wrote: > Using a 4.9 kernel, trying to boot a kernel using an eMMC based rootfs will > result in a crash > > The message preceeding the crash is: > > [3.285566] VFS: Cannot open root device "mmcblk0p9" or > unknown-block(0,0): error -6 > [

Re: Cannot boot with rootfs from eMMC if maxcpus=1

On 11/09/2017 08:14 AM, Richard Schmitt wrote: > Using a 4.9 kernel, trying to boot a kernel using an eMMC based rootfs will > result in a crash > > The message preceeding the crash is: > > [3.285566] VFS: Cannot open root device "mmcblk0p9" or > unknown-block(0,0): error -6 > [

[PULL REQUEST] nfsd changes for 4.15

Please pull nfsd changes for 4.15 from: git://linux-nfs.org/~bfields/linux.git tags/nfsd-4.15 Lots of good bugfixes, including: - fix a number of races in the NFSv4+ state code. - fix some shutdown crashes in multiple-network-namespace cases. - relax our 4.1 session

[PULL REQUEST] nfsd changes for 4.15

Please pull nfsd changes for 4.15 from: git://linux-nfs.org/~bfields/linux.git tags/nfsd-4.15 Lots of good bugfixes, including: - fix a number of races in the NFSv4+ state code. - fix some shutdown crashes in multiple-network-namespace cases. - relax our 4.1 session

Re: [GIT PULL] platform-drivers-x86 for 4.15-1

On Sat, Nov 18, 2017 at 10:09 AM, Andy Shevchenko wrote: > > Here is the collected material against Platform Drivers x86 subsystem. > It's rather bit busy cycle for PDx86, mostly due to Dell SMBIOS driver > activity. So I note that you seem to use the same

Re: [GIT PULL] platform-drivers-x86 for 4.15-1

On Sat, Nov 18, 2017 at 10:09 AM, Andy Shevchenko wrote: > > Here is the collected material against Platform Drivers x86 subsystem. > It's rather bit busy cycle for PDx86, mostly due to Dell SMBIOS driver > activity. So I note that you seem to use the same summary script that Darren used. Guys,

Re: [PATCH PREEMPT RT] rt-mutex: fix deadlock in device mapper

On Fri, 2017-11-17 at 15:57 +0100, Sebastian Siewior wrote: > On 2017-11-13 12:56:53 [-0500], Mikulas Patocka wrote: > > Hi > Hi, > > > I'm submitting this patch for the CONFIG_PREEMPT_RT patch. It fixes > > deadlocks in device mapper when real time preemption is used. > > applied, thank you.

Re: [PATCH PREEMPT RT] rt-mutex: fix deadlock in device mapper

On Fri, 2017-11-17 at 15:57 +0100, Sebastian Siewior wrote: > On 2017-11-13 12:56:53 [-0500], Mikulas Patocka wrote: > > Hi > Hi, > > > I'm submitting this patch for the CONFIG_PREEMPT_RT patch. It fixes > > deadlocks in device mapper when real time preemption is used. > > applied, thank you.

Re: [PATCH] input: remove unneeded DRIVER_LICENSE #defines

On Sat, Nov 18, 2017 at 11:27:24AM +0100, Greg Kroah-Hartman wrote: > On Fri, Nov 17, 2017 at 12:33:13PM -0800, Dmitry Torokhov wrote: > > On Fri, Nov 17, 2017 at 03:17:20PM +0100, Greg Kroah-Hartman wrote: > > > There is no need to #define the license of the driver, just put it in > > > the

Re: Commit fcd8843c40 breaks old compilers

On 11/18/2017 01:12 PM, Trond Myklebust wrote: Sigh OK, how about something like the following then: { .data = { 0xff, 0xff, 0xff, 0xff, 0 }, } Yes, this does build. diff --git a/fs/nfs/nfs4state.c b/fs/nfs/nfs4state.c index 54fd56d..daa6085 100644 --- a/fs/nfs/nfs4state.c +++

Re: [PATCH] input: remove unneeded DRIVER_LICENSE #defines

On Sat, Nov 18, 2017 at 11:27:24AM +0100, Greg Kroah-Hartman wrote: > On Fri, Nov 17, 2017 at 12:33:13PM -0800, Dmitry Torokhov wrote: > > On Fri, Nov 17, 2017 at 03:17:20PM +0100, Greg Kroah-Hartman wrote: > > > There is no need to #define the license of the driver, just put it in > > > the

Re: Commit fcd8843c40 breaks old compilers

On 11/18/2017 01:12 PM, Trond Myklebust wrote: Sigh OK, how about something like the following then: { .data = { 0xff, 0xff, 0xff, 0xff, 0 }, } Yes, this does build. diff --git a/fs/nfs/nfs4state.c b/fs/nfs/nfs4state.c index 54fd56d..daa6085 100644 --- a/fs/nfs/nfs4state.c +++

Re: [PATCH 01/10 v3] Input: ep93xx_keypad: Fix platform_get_irq's error checking

On Sat, Nov 18, 2017 at 04:25:08PM +0530, Arvind Yadav wrote: > The platform_get_irq() function returns negative if an error occurs. > zero or positive number on success. platform_get_irq() error checking > for zero is not correct. > > Signed-off-by: Arvind Yadav > ---

Re: [PATCH 01/10 v3] Input: ep93xx_keypad: Fix platform_get_irq's error checking

On Sat, Nov 18, 2017 at 04:25:08PM +0530, Arvind Yadav wrote: > The platform_get_irq() function returns negative if an error occurs. > zero or positive number on success. platform_get_irq() error checking > for zero is not correct. > > Signed-off-by: Arvind Yadav > --- > changes in v2: >

Re: [PATCH 5/10 v2] Input: cpcap-pwrbutton: Handle return value of platform_get_irq

On Sat, Nov 18, 2017 at 08:21:22AM +, Russell King - ARM Linux wrote: > On Sat, Nov 18, 2017 at 02:36:53AM +0530, Arvind Yadav wrote: > > platform_get_irq() can fail here and we must check its return value. > > The test should be <= 0, and you need to return an error code for the > 0 case.

Re: [PATCH 5/10 v2] Input: cpcap-pwrbutton: Handle return value of platform_get_irq

On Sat, Nov 18, 2017 at 08:21:22AM +, Russell King - ARM Linux wrote: > On Sat, Nov 18, 2017 at 02:36:53AM +0530, Arvind Yadav wrote: > > platform_get_irq() can fail here and we must check its return value. > > The test should be <= 0, and you need to return an error code for the > 0 case.

Re: mm/percpu.c: use smarter memory allocation for struct pcpu_alloc_info (crisv32 hang)

Hi, On Tue, Oct 03, 2017 at 06:29:49PM -0400, Nicolas Pitre wrote: > On Tue, 3 Oct 2017, Tejun Heo wrote: > > > On Tue, Oct 03, 2017 at 04:57:44PM -0400, Nicolas Pitre wrote: > > > This can be much smaller than a page on very small memory systems. > > > Always rounding up the size to a page is

Re: mm/percpu.c: use smarter memory allocation for struct pcpu_alloc_info (crisv32 hang)

Hi, On Tue, Oct 03, 2017 at 06:29:49PM -0400, Nicolas Pitre wrote: > On Tue, 3 Oct 2017, Tejun Heo wrote: > > > On Tue, Oct 03, 2017 at 04:57:44PM -0400, Nicolas Pitre wrote: > > > This can be much smaller than a page on very small memory systems. > > > Always rounding up the size to a page is

[GIT PULL] platform-drivers-x86 for 4.15-1

Hi Linus, Here is the collected material against Platform Drivers x86 subsystem. It's rather bit busy cycle for PDx86, mostly due to Dell SMBIOS driver activity. During merge it will get a conflict CONFLICT (content): Merge conflict in Documentation/admin-guide/thunderbolt.rst that is pretty

[GIT PULL] platform-drivers-x86 for 4.15-1

Hi Linus, Here is the collected material against Platform Drivers x86 subsystem. It's rather bit busy cycle for PDx86, mostly due to Dell SMBIOS driver activity. During merge it will get a conflict CONFLICT (content): Merge conflict in Documentation/admin-guide/thunderbolt.rst that is pretty

Re: [PATCH v18 5/6] vfio: ABI for mdev display dma-buf operation

On Sat, 18 Nov 2017 23:29:31 +0530 Kirti Wankhede wrote: > Extremely sorry for the delay. > This works for VFIO_GFX_PLANE_TYPE_REGION. Tested with local changes. > > Reviewed-by: Kirti Wankhede With that, Acked-by: Alex Williamson

Re: [PATCH v18 5/6] vfio: ABI for mdev display dma-buf operation

On Sat, 18 Nov 2017 23:29:31 +0530 Kirti Wankhede wrote: > Extremely sorry for the delay. > This works for VFIO_GFX_PLANE_TYPE_REGION. Tested with local changes. > > Reviewed-by: Kirti Wankhede With that, Acked-by: Alex Williamson > On 11/18/2017 9:00 PM, Alex Williamson wrote: > > > >

Re: Commit fcd8843c40 breaks old compilers

On Sat, 2017-11-18 at 13:07 -0500, Boris Ostrovsky wrote: > > On 11/18/2017 12:39 PM, Trond Myklebust wrote: > > On Sat, 2017-11-18 at 12:19 -0500, Boris Ostrovsky wrote: > > > Commit fcd8843c406b46433857ae45e5e9d84b01a7d20b breaks on older > > > compilers which cannot process initializers for

Re: Commit fcd8843c40 breaks old compilers

On Sat, 2017-11-18 at 13:07 -0500, Boris Ostrovsky wrote: > > On 11/18/2017 12:39 PM, Trond Myklebust wrote: > > On Sat, 2017-11-18 at 12:19 -0500, Boris Ostrovsky wrote: > > > Commit fcd8843c406b46433857ae45e5e9d84b01a7d20b breaks on older > > > compilers which cannot process initializers for

Re: Commit fcd8843c40 breaks old compilers

On 11/18/2017 12:39 PM, Trond Myklebust wrote: On Sat, 2017-11-18 at 12:19 -0500, Boris Ostrovsky wrote: Commit fcd8843c406b46433857ae45e5e9d84b01a7d20b breaks on older compilers which cannot process initializers for anonymous structures: +const nfs4_stateid invalid_stateid = { + { +

Re: Commit fcd8843c40 breaks old compilers

On 11/18/2017 12:39 PM, Trond Myklebust wrote: On Sat, 2017-11-18 at 12:19 -0500, Boris Ostrovsky wrote: Commit fcd8843c406b46433857ae45e5e9d84b01a7d20b breaks on older compilers which cannot process initializers for anonymous structures: +const nfs4_stateid invalid_stateid = { + { +

RFC: Copying Device Tree File into reserved area of VMLINUX before deployment

I noticed when checking out the OpenWRT support for the board that they have a method to avoid having to pass the device tree address to the kernel, and can thus boot device tree based kernels with U-boots that does not support device trees. Is this something that would be considered useful

RFC: Copying Device Tree File into reserved area of VMLINUX before deployment

I noticed when checking out the OpenWRT support for the board that they have a method to avoid having to pass the device tree address to the kernel, and can thus boot device tree based kernels with U-boots that does not support device trees. Is this something that would be considered useful

Re: [PATCH v18 5/6] vfio: ABI for mdev display dma-buf operation

Extremely sorry for the delay. This works for VFIO_GFX_PLANE_TYPE_REGION. Tested with local changes. Reviewed-by: Kirti Wankhede Thanks, Kirti On 11/18/2017 9:00 PM, Alex Williamson wrote: > > Kirti? > > On Wed, 15 Nov 2017 21:11:42 -0700 > Alex Williamson

Re: [PATCH v18 5/6] vfio: ABI for mdev display dma-buf operation

Extremely sorry for the delay. This works for VFIO_GFX_PLANE_TYPE_REGION. Tested with local changes. Reviewed-by: Kirti Wankhede Thanks, Kirti On 11/18/2017 9:00 PM, Alex Williamson wrote: > > Kirti? > > On Wed, 15 Nov 2017 21:11:42 -0700 > Alex Williamson wrote: > >> On Thu, 16 Nov 2017

[PATCH] Staging: comedi: adl_pci9118.c : fixed code style issue

Removed uneccessary parantheses which were sorrounding two if-statements. Signed-off-by: Fabian Baumanis ---  drivers/staging/comedi/drivers/adl_pci9118.c | 3 +--  1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/staging/comedi/drivers/adl_pci9118.c

[PATCH] Staging: comedi: adl_pci9118.c : fixed code style issue

Removed uneccessary parantheses which were sorrounding two if-statements. Signed-off-by: Fabian Baumanis ---  drivers/staging/comedi/drivers/adl_pci9118.c | 3 +--  1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/staging/comedi/drivers/adl_pci9118.c

Re: Commit fcd8843c40 breaks old compilers

On Sat, 2017-11-18 at 12:19 -0500, Boris Ostrovsky wrote: > Commit fcd8843c406b46433857ae45e5e9d84b01a7d20b breaks on older > compilers which cannot process initializers for anonymous structures: > > +const nfs4_stateid invalid_stateid = { > + { > + .seqid =

Re: Commit fcd8843c40 breaks old compilers

On Sat, 2017-11-18 at 12:19 -0500, Boris Ostrovsky wrote: > Commit fcd8843c406b46433857ae45e5e9d84b01a7d20b breaks on older > compilers which cannot process initializers for anonymous structures: > > +const nfs4_stateid invalid_stateid = { > + { > + .seqid =

Commit fcd8843c40 breaks old compilers

Commit fcd8843c406b46433857ae45e5e9d84b01a7d20b breaks on older compilers which cannot process initializers for anonymous structures: +const nfs4_stateid invalid_stateid = { + { + .seqid = cpu_to_be32(0xU), + .other = { 0 }, + }, + .type =

Commit fcd8843c40 breaks old compilers

Commit fcd8843c406b46433857ae45e5e9d84b01a7d20b breaks on older compilers which cannot process initializers for anonymous structures: +const nfs4_stateid invalid_stateid = { + { + .seqid = cpu_to_be32(0xU), + .other = { 0 }, + }, + .type =

Re: [RFC PATCH 7/7] ASoC: Intel: boards: align/fix SKL/BXT/KBL Kconfigs

On Fri, 2017-11-17 at 18:02 -0600, Pierre-Louis Bossart wrote: > No reason why SND_SOC_INTEL_SST should be set here. > Also make sure same dependencies are used everywhere (only last one > has SPI > in addition) Regarding to my comment against previous patch... > config

Re: [RFC PATCH 7/7] ASoC: Intel: boards: align/fix SKL/BXT/KBL Kconfigs

On Fri, 2017-11-17 at 18:02 -0600, Pierre-Louis Bossart wrote: > No reason why SND_SOC_INTEL_SST should be set here. > Also make sure same dependencies are used everywhere (only last one > has SPI > in addition) Regarding to my comment against previous patch... > config

Re: [RFC PATCH 6/7] ASoC: Intel: boards: align Kconfig configurations for HiFi2

On Fri, 2017-11-17 at 18:02 -0600, Pierre-Louis Bossart wrote: > Make sure all the configs are aligned > Also add the missing dependencies on SOC_ACPI stuff used to fix > DAI names based on HID. > > FIXME: not sure why X86_INTEL_LPSS is needed in a machine > driver config, should it be back to

Re: [RFC PATCH 6/7] ASoC: Intel: boards: align Kconfig configurations for HiFi2

On Fri, 2017-11-17 at 18:02 -0600, Pierre-Louis Bossart wrote: > Make sure all the configs are aligned > Also add the missing dependencies on SOC_ACPI stuff used to fix > DAI names based on HID. > > FIXME: not sure why X86_INTEL_LPSS is needed in a machine > driver config, should it be back to

Re: [RFC PATCH 2/7] ASoC: Intel: Kconfig: Simplify-clarify ACPI/PCI dependencies

On Sat, 2017-11-18 at 18:53 +0200, Andy Shevchenko wrote: > On Fri, 2017-11-17 at 18:01 -0600, Pierre-Louis Bossart wrote: > > PCI/ACPI selections should not happen in Kconfig for machine > > drivers, > > move to SOC selections. > > > > Add distinction between PCI and ACPI HiFi2 platforms. > >

Re: [RFC PATCH 2/7] ASoC: Intel: Kconfig: Simplify-clarify ACPI/PCI dependencies

On Sat, 2017-11-18 at 18:53 +0200, Andy Shevchenko wrote: > On Fri, 2017-11-17 at 18:01 -0600, Pierre-Louis Bossart wrote: > > PCI/ACPI selections should not happen in Kconfig for machine > > drivers, > > move to SOC selections. > > > > Add distinction between PCI and ACPI HiFi2 platforms. > >

Re: [RFC PATCH 2/7] ASoC: Intel: Kconfig: Simplify-clarify ACPI/PCI dependencies

On Fri, 2017-11-17 at 18:01 -0600, Pierre-Louis Bossart wrote: > PCI/ACPI selections should not happen in Kconfig for machine drivers, > move to SOC selections. > > Add distinction between PCI and ACPI HiFi2 platforms. > The PCI-based > platforms may be removed at some point since Medfield is

Re: [RFC PATCH 2/7] ASoC: Intel: Kconfig: Simplify-clarify ACPI/PCI dependencies

On Fri, 2017-11-17 at 18:01 -0600, Pierre-Louis Bossart wrote: > PCI/ACPI selections should not happen in Kconfig for machine drivers, > move to SOC selections. > > Add distinction between PCI and ACPI HiFi2 platforms. > The PCI-based > platforms may be removed at some point since Medfield is

Re: [RFC PATCH 1/7] ASoC: Intel: Fix Kconfig

On Sat, 18 Nov 2017 01:01:56 +0100, Pierre-Louis Bossart wrote: > > +if SND_SOC_INTEL_BAYTRAIL > > config SND_SOC_INTEL_BYT_MAX98090_MACH > tristate "ASoC Audio driver for Intel Baytrail with MAX98090 codec" > + default n default=n is superfluous, can be dropped. > depends on

Re: [RFC PATCH 1/7] ASoC: Intel: Fix Kconfig

On Sat, 18 Nov 2017 01:01:56 +0100, Pierre-Louis Bossart wrote: > > +if SND_SOC_INTEL_BAYTRAIL > > config SND_SOC_INTEL_BYT_MAX98090_MACH > tristate "ASoC Audio driver for Intel Baytrail with MAX98090 codec" > + default n default=n is superfluous, can be dropped. > depends on

Re: [PATCH v2] iio: mma8452: replace license description with SPDX specifier

On Sat, Nov 18, 2017 at 4:53 PM, Jonathan Cameron wrote: > On Sat, 18 Nov 2017 10:10:11 +0100 > Martin Kepplinger wrote: > >> This replaces the custom license information text with the appropriate >> SPDX identifier. While the information here stays the same,

Re: [PATCH v2] iio: mma8452: replace license description with SPDX specifier

On Sat, Nov 18, 2017 at 4:53 PM, Jonathan Cameron wrote: > On Sat, 18 Nov 2017 10:10:11 +0100 > Martin Kepplinger wrote: > >> This replaces the custom license information text with the appropriate >> SPDX identifier. While the information here stays the same, it is easier >> to read. >> >>

[PATCH] staging: comedi: ni_atmio: fix license warning.

Resolving license check warning for drivers/staging/comedi. Added the license definitions present in the rest of the module and made sure it's aligned with the license (GPL) in the comments for the affected file (ni_atmio.c). Original warning: WARNING: modpost: missing MODULE_LICENSE() in

[PATCH] staging: comedi: ni_atmio: fix license warning.

Resolving license check warning for drivers/staging/comedi. Added the license definitions present in the rest of the module and made sure it's aligned with the license (GPL) in the comments for the affected file (ni_atmio.c). Original warning: WARNING: modpost: missing MODULE_LICENSE() in

Re: [v4,3/3] hwmon: (w83773g) Add documentation

On Mon, Nov 13, 2017 at 11:27:34AM +0800, Lei YU wrote: > Add documentation for the w83773g driver. > > Signed-off-by: Lei YU Applied to hwmon-next. Thanks, Guenter

Re: [v4,3/3] hwmon: (w83773g) Add documentation

On Mon, Nov 13, 2017 at 11:27:34AM +0800, Lei YU wrote: > Add documentation for the w83773g driver. > > Signed-off-by: Lei YU Applied to hwmon-next. Thanks, Guenter

Re: [v4,2/3] drivers: hwmon: Add W83773G driver

On Mon, Nov 13, 2017 at 11:27:33AM +0800, Lei YU wrote: > Nuvoton W83773G is a hardware monitor IC providing one local > temperature and two remote temperature sensors. > > Signed-off-by: Lei YU Applied to hwmon-next. Thanks, Guenter > --- > v2: > - Rewrite the driver

Re: [v4,2/3] drivers: hwmon: Add W83773G driver

On Mon, Nov 13, 2017 at 11:27:33AM +0800, Lei YU wrote: > Nuvoton W83773G is a hardware monitor IC providing one local > temperature and two remote temperature sensors. > > Signed-off-by: Lei YU Applied to hwmon-next. Thanks, Guenter > --- > v2: > - Rewrite the driver using regmap > - Add

Re: [PATCH v3 3/4] iio: adc: at91-sama5d2_adc: add support for DMA

On Wed, 15 Nov 2017 14:56:47 +0200 Eugen Hristev wrote: > Added support for DMA transfers. The implementation uses the user watermark > to decide whether DMA will be used or not. For watermark 1, DMA will not be > used. If watermark is bigger, DMA will be used. >

Re: [PATCH v3 1/4] dt-bindings: iio: at91-sama5d2_adc: add optional dma property

On Wed, 15 Nov 2017 09:27:46 -0600 Rob Herring wrote: > On Wed, Nov 15, 2017 at 02:56:45PM +0200, Eugen Hristev wrote: > > Added property for DMA configuration of the device. > > > > Signed-off-by: Eugen Hristev > > --- > > Changes in v3: > >

Re: [PATCH v3 3/4] iio: adc: at91-sama5d2_adc: add support for DMA

On Wed, 15 Nov 2017 14:56:47 +0200 Eugen Hristev wrote: > Added support for DMA transfers. The implementation uses the user watermark > to decide whether DMA will be used or not. For watermark 1, DMA will not be > used. If watermark is bigger, DMA will be used. > Sysfs attributes are created to

Re: [PATCH v3 1/4] dt-bindings: iio: at91-sama5d2_adc: add optional dma property

On Wed, 15 Nov 2017 09:27:46 -0600 Rob Herring wrote: > On Wed, Nov 15, 2017 at 02:56:45PM +0200, Eugen Hristev wrote: > > Added property for DMA configuration of the device. > > > > Signed-off-by: Eugen Hristev > > --- > > Changes in v3: > > None, but we discussed on the ML about whether we

Re: A test of the philosophical impact.. Behaviour problems of "Gnu-Zealots" = Illegal Unix Rip.

Den 11/12/2017 11:53, skrev Ywe Cærlyn: Den 11/9/2017 11:55, skrev Ywe Cærlyn: Den 11/6/2017 19:13, skrev Ywe Cærlyn: Den 11/6/2017 11:00, skrev Ywe Cærlyn: Den 11/4/2017 23:53, skrev Ywe Cærlyn: Den 11/3/2017 07:46, skrev Ywe Cærlyn: Den 10/29/2017 17:21, skrev Ywe Cærlyn: Den 10/29/2017

Re: A test of the philosophical impact.. Behaviour problems of "Gnu-Zealots" = Illegal Unix Rip.

Den 11/12/2017 11:53, skrev Ywe Cærlyn: Den 11/9/2017 11:55, skrev Ywe Cærlyn: Den 11/6/2017 19:13, skrev Ywe Cærlyn: Den 11/6/2017 11:00, skrev Ywe Cærlyn: Den 11/4/2017 23:53, skrev Ywe Cærlyn: Den 11/3/2017 07:46, skrev Ywe Cærlyn: Den 10/29/2017 17:21, skrev Ywe Cærlyn: Den 10/29/2017

Re: [PATCH v2] iio: mma8452: replace license description with SPDX specifier

On Sat, 18 Nov 2017 10:10:11 +0100 Martin Kepplinger wrote: > This replaces the custom license information text with the appropriate > SPDX identifier. While the information here stays the same, it is easier > to read. > > Signed-off-by: Martin Kepplinger

Re: [PATCH v2] iio: mma8452: replace license description with SPDX specifier

On Sat, 18 Nov 2017 10:10:11 +0100 Martin Kepplinger wrote: > This replaces the custom license information text with the appropriate > SPDX identifier. While the information here stays the same, it is easier > to read. > > Signed-off-by: Martin Kepplinger > Acked-by: Peter Meerwald-Stadler

<    1   2   3   4   5   6   >