[patch 2/3] staging: speakup: use tty_kopen instead of tty_open_by_driver

This patch replaces call to tty_open_by_driver with a tty_kopen. Signed-off-by: Okash Khawaja --- drivers/staging/speakup/spk_ttyio.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/drivers/staging/speakup/spk_ttyio.c +++

[for-next][PATCH 0/4] tracing: A few more changes for 4.13

git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git for-next Head SHA1: 29b1a8ad7df4528b862a79e3d5fb0936f4d199c7 Joel Fernandes (3): tracing: Treat recording comm for idle task as a success tracing: Treat recording tgid for idle task as a success tracing:

[for-next][PATCH 0/4] tracing: A few more changes for 4.13

git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git for-next Head SHA1: 29b1a8ad7df4528b862a79e3d5fb0936f4d199c7 Joel Fernandes (3): tracing: Treat recording comm for idle task as a success tracing: Treat recording tgid for idle task as a success tracing:

[patch 2/3] staging: speakup: use tty_kopen instead of tty_open_by_driver

This patch replaces call to tty_open_by_driver with a tty_kopen. Signed-off-by: Okash Khawaja --- drivers/staging/speakup/spk_ttyio.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/drivers/staging/speakup/spk_ttyio.c +++ b/drivers/staging/speakup/spk_ttyio.c @@ -164,7 +164,7

Re: spmi: pmic-arb: Always allocate ppid_to_apid table

On Dienstag, 27. Juni 2017 04:17:46 CEST Stephen Boyd wrote: > After commit 7f1d4e58dabb ("spmi: pmic-arb: optimize table > lookups") we always need the ppid_to_apid table regardless of the > version of pmic arbiter we have. Otherwise, we will try to deref > the array when we don't allocate it on

Re: spmi: pmic-arb: Always allocate ppid_to_apid table

On Dienstag, 27. Juni 2017 04:17:46 CEST Stephen Boyd wrote: > After commit 7f1d4e58dabb ("spmi: pmic-arb: optimize table > lookups") we always need the ppid_to_apid table regardless of the > version of pmic arbiter we have. Otherwise, we will try to deref > the array when we don't allocate it on

[PATCH] MAINTAINERS: move the befs tree to kernel.org

Updating the location of the befs git tree and my email address. Signed-off-by: Luis de Bethencourt --- Hello, The currently listed email address isn't valid anymore due to a job change. It felt like a good moment to request a kernel.org account (thanks Konstantin for the

[PATCH] MAINTAINERS: move the befs tree to kernel.org

Updating the location of the befs git tree and my email address. Signed-off-by: Luis de Bethencourt --- Hello, The currently listed email address isn't valid anymore due to a job change. It felt like a good moment to request a kernel.org account (thanks Konstantin for the prompt response and

[PATCH] cifs: Clean up unused variables in smb2pdu.c

There are multiple unused variables struct TCP_Server_Info *server defined in many methods in smb2pdu.c. They should be removed and related logic simplified. Signed-off-by: Christos Gkekas --- fs/cifs/smb2pdu.c | 35 +++ 1 file changed, 7

[PATCH] cifs: Clean up unused variables in smb2pdu.c

There are multiple unused variables struct TCP_Server_Info *server defined in many methods in smb2pdu.c. They should be removed and related logic simplified. Signed-off-by: Christos Gkekas --- fs/cifs/smb2pdu.c | 35 +++ 1 file changed, 7 insertions(+), 28

Re: [PATCH] x86/boot/KASLR: exclude EFI_BOOT_SERVICES_{CODE|DATA} from KASLR's choice

On 07/07/17 at 11:56am, Matt Fleming wrote: > On Fri, 07 Jul, at 11:07:59AM, Baoquan He wrote: > > On 07/06/17 at 03:57pm, Matt Fleming wrote: > > > On Thu, 06 Jul, at 08:31:07AM, Naoya Horiguchi wrote: > > > > + for (i = 0; i < nr_desc; i++) { > > > > + md = (efi_memory_desc_t

Re: [PATCH] x86/boot/KASLR: exclude EFI_BOOT_SERVICES_{CODE|DATA} from KASLR's choice

On 07/07/17 at 11:56am, Matt Fleming wrote: > On Fri, 07 Jul, at 11:07:59AM, Baoquan He wrote: > > On 07/06/17 at 03:57pm, Matt Fleming wrote: > > > On Thu, 06 Jul, at 08:31:07AM, Naoya Horiguchi wrote: > > > > + for (i = 0; i < nr_desc; i++) { > > > > + md = (efi_memory_desc_t

Re: [PATCH] spi: pxa2xx: Only claim CS GPIOs when the slave device is created

On 2017-07-09 11:55, Andy Shevchenko wrote: > On Sun, Jul 9, 2017 at 12:30 PM, Jan Kiszka wrote: >> On 2017-07-08 23:48, Andy Shevchenko wrote: >>> On Sat, Jul 8, 2017 at 11:41 AM, Jan Kiszka wrote: From: Jan Kiszka

Re: [PATCH] spi: pxa2xx: Only claim CS GPIOs when the slave device is created

On 2017-07-09 11:55, Andy Shevchenko wrote: > On Sun, Jul 9, 2017 at 12:30 PM, Jan Kiszka wrote: >> On 2017-07-08 23:48, Andy Shevchenko wrote: >>> On Sat, Jul 8, 2017 at 11:41 AM, Jan Kiszka wrote: From: Jan Kiszka Avoid hogging chip select GPIOs just because they are listed for

Re: [PATCH] spi: pxa2xx: Only claim CS GPIOs when the slave device is created

On Sun, Jul 9, 2017 at 12:30 PM, Jan Kiszka wrote: > On 2017-07-08 23:48, Andy Shevchenko wrote: >> On Sat, Jul 8, 2017 at 11:41 AM, Jan Kiszka wrote: >>> From: Jan Kiszka >>> >>> Avoid hogging chip select GPIOs just because they are

Re: [PATCH] spi: pxa2xx: Only claim CS GPIOs when the slave device is created

On Sun, Jul 9, 2017 at 12:30 PM, Jan Kiszka wrote: > On 2017-07-08 23:48, Andy Shevchenko wrote: >> On Sat, Jul 8, 2017 at 11:41 AM, Jan Kiszka wrote: >>> From: Jan Kiszka >>> >>> Avoid hogging chip select GPIOs just because they are listed for the >>> master. They might be mulitplexed and, if

Re: [PATCH] spi: pxa2xx: Only claim CS GPIOs when the slave device is created

On 2017-07-08 23:48, Andy Shevchenko wrote: > On Sat, Jul 8, 2017 at 11:41 AM, Jan Kiszka wrote: >> From: Jan Kiszka >> >> Avoid hogging chip select GPIOs just because they are listed for the >> master. They might be mulitplexed and, if no slave device

Re: [PATCH] spi: pxa2xx: Only claim CS GPIOs when the slave device is created

On 2017-07-08 23:48, Andy Shevchenko wrote: > On Sat, Jul 8, 2017 at 11:41 AM, Jan Kiszka wrote: >> From: Jan Kiszka >> >> Avoid hogging chip select GPIOs just because they are listed for the >> master. They might be mulitplexed and, if no slave device is attached, >> used for different

[GIT pull] x86 updates for 4.13

Linus, please pull the latest x86-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-urgent-for-linus The x86 updates contain: - A fix for a longstanding PAT bug, where PAT was reported on CPUs that do not support it, which leads to

[GIT pull] x86 updates for 4.13

Linus, please pull the latest x86-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-urgent-for-linus The x86 updates contain: - A fix for a longstanding PAT bug, where PAT was reported on CPUs that do not support it, which leads to

[PATCH] ARM: imx: constify gpio and pins.

gpios and pins are not supposed to change at runtime. All functions working with gpios provided by work with const gpio. Pins is working with 'mxc_iomux_setup_multiple_pins( const unsigned int *pin_list, ...)'. So mark the non-const structs as const. Signed-off-by: Arvind Yadav

[PATCH] ARM: imx: constify gpio and pins.

gpios and pins are not supposed to change at runtime. All functions working with gpios provided by work with const gpio. Pins is working with 'mxc_iomux_setup_multiple_pins( const unsigned int *pin_list, ...)'. So mark the non-const structs as const. Signed-off-by: Arvind Yadav ---

[GIT pull] timers update for 4.13

Linus, please pull the latest timers-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers-urgent-for-linus Add Frederic Weisbecker as NOHZ/dyntick maintainer. Thanks, tglx --> Ingo Molnar (1): MAINTAINERS: Add

[GIT pull] timers update for 4.13

Linus, please pull the latest timers-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers-urgent-for-linus Add Frederic Weisbecker as NOHZ/dyntick maintainer. Thanks, tglx --> Ingo Molnar (1): MAINTAINERS: Add

[GIT pull] smp/hotplug updates for 4.13

Linus, please pull the latest smp-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git smp-urgent-for-linus A single fix for a brown paperbag bug: - The unparking of the initial percpu threads of an upcoming CPU happens right now on the idle task,

[GIT pull] smp/hotplug updates for 4.13

Linus, please pull the latest smp-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git smp-urgent-for-linus A single fix for a brown paperbag bug: - The unparking of the initial percpu threads of an upcoming CPU happens right now on the idle task,

Re: [RFC PATCH] x86: enable dead code and data elimination (LTO)

* Nicholas Piggin wrote: > FYI, easiest way to check if you forgot to KEEP a linker table is > to look at `readelf -S vmlinux` differences, and to see what is > being trimmed, look at nm differences or use --print-gc-sections > LD option to see what symbols you're trimming.

Re: [RFC PATCH] x86: enable dead code and data elimination (LTO)

* Nicholas Piggin wrote: > FYI, easiest way to check if you forgot to KEEP a linker table is > to look at `readelf -S vmlinux` differences, and to see what is > being trimmed, look at nm differences or use --print-gc-sections > LD option to see what symbols you're trimming. Linker tables, >

[GIT pull] scheduler updates for 4.13

Linus, please pull the latest sched-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched-urgent-for-linus This scheduler update provides: - The (hopefully) final fix for the vtime accounting issues which were around for quite some time

[GIT pull] scheduler updates for 4.13

Linus, please pull the latest sched-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched-urgent-for-linus This scheduler update provides: - The (hopefully) final fix for the vtime accounting issues which were around for quite some time

[GIT pull] perf updates for 4.13

Linus, please pull the latest perf-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf-urgent-for-linus A couple of fixes for perf and kprobes: - Add he missing exclude_kernel attribute for the precise_ip level so !CAP_SYS_ADMIN users get

[GIT pull] perf updates for 4.13

Linus, please pull the latest perf-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf-urgent-for-linus A couple of fixes for perf and kprobes: - Add he missing exclude_kernel attribute for the precise_ip level so !CAP_SYS_ADMIN users get

[GIT pull] locking updates for 4.13

Linus, please pull the latest locking-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking-urgent-for-linus Two fixlets for the locking code: - Fix the EINTR logic in rwsem-spinlock to avoid double locking by a writer and a reader - Add

[GIT pull] locking updates for 4.13

Linus, please pull the latest locking-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking-urgent-for-linus Two fixlets for the locking code: - Fix the EINTR logic in rwsem-spinlock to avoid double locking by a writer and a reader - Add

[GIT pull] irq updates for 4.13

Linus, please pull the latest irq-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq-urgent-for-linus This update contains: - A few fixes mopping up the fallout of the big irq overhaul - Move the interrupt resource management logic out of the

[GIT pull] irq updates for 4.13

Linus, please pull the latest irq-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq-urgent-for-linus This update contains: - A few fixes mopping up the fallout of the big irq overhaul - Move the interrupt resource management logic out of the

[GIT pull] core updates for 4.13

Linus, please pull the latest core-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git core-urgent-for-linus A fix to the objtool sibling call detection logic to distinguish normal jumps inside a function from a real sibling call. Thanks, tglx

[GIT pull] core updates for 4.13

Linus, please pull the latest core-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git core-urgent-for-linus A fix to the objtool sibling call detection logic to distinguish normal jumps inside a function from a real sibling call. Thanks, tglx

[PATCH RESEND] arm64: arch_timer: fix the infinite recursion when enable ftrace and erratum workaround

When enable preempt and debug ftrace, and perform the following steps, the system will hang: mount -t debugfs nodev /sys/kernel/debug/ cd /sys/kernel/debug/tracing/ echo function_graph > current_tracer This is because tracing the preempt_disable/enable calls would cause trace_clock() which would

[PATCH RESEND] arm64: arch_timer: fix the infinite recursion when enable ftrace and erratum workaround

When enable preempt and debug ftrace, and perform the following steps, the system will hang: mount -t debugfs nodev /sys/kernel/debug/ cd /sys/kernel/debug/tracing/ echo function_graph > current_tracer This is because tracing the preempt_disable/enable calls would cause trace_clock() which would

Re: [PATCH] arm64: arch_timer: fix the infinite recursion when enable ftrace and erratum workaround

On 2017/7/6 22:35, Mark Rutland wrote: > On Thu, Jul 06, 2017 at 08:49:33PM +0800, Ding Tianhong wrote: >> When enable preempt and ftrace, and perform the following steps, the system >> will hang: >> mount -t debugfs nodev /sys/kernel/debug/ >> cd /sys/kernel/debug/tracing/ >> echo

Re: [PATCH] arm64: arch_timer: fix the infinite recursion when enable ftrace and erratum workaround

On 2017/7/6 22:35, Mark Rutland wrote: > On Thu, Jul 06, 2017 at 08:49:33PM +0800, Ding Tianhong wrote: >> When enable preempt and ftrace, and perform the following steps, the system >> will hang: >> mount -t debugfs nodev /sys/kernel/debug/ >> cd /sys/kernel/debug/tracing/ >> echo

[PATCH v2] drm/sun4i: Implement drm_driver lastclose to restore fbdev console

The drm_driver lastclose callback is called when the last userspace DRM client has closed. Call drm_fbdev_cma_restore_mode to restore the fbdev console otherwise the fbdev console will stop working. Signed-off-by: Jonathan Liu --- Changes for v2: - Rename sun4i_drm_lastclose

[PATCH v2] drm/sun4i: Implement drm_driver lastclose to restore fbdev console

The drm_driver lastclose callback is called when the last userspace DRM client has closed. Call drm_fbdev_cma_restore_mode to restore the fbdev console otherwise the fbdev console will stop working. Signed-off-by: Jonathan Liu --- Changes for v2: - Rename sun4i_drm_lastclose to

[PATCH] drm/sun4i: Implement drm_driver lastclose to restore fbdev console

The drm_driver lastclose callback is called when the last userspace DRM client has closed. Call drm_fbdev_cma_restore_mode to restore the fbdev console otherwise the fbdev console will stop working. Signed-off-by: Jonathan Liu --- drivers/gpu/drm/sun4i/sun4i_drv.c | 8

[PATCH] drm/sun4i: Implement drm_driver lastclose to restore fbdev console

The drm_driver lastclose callback is called when the last userspace DRM client has closed. Call drm_fbdev_cma_restore_mode to restore the fbdev console otherwise the fbdev console will stop working. Signed-off-by: Jonathan Liu --- drivers/gpu/drm/sun4i/sun4i_drv.c | 8 1 file changed,

Re: [PATCH v2 1/1] mux: consumer: Add dummy functions for !CONFIG_MULTIPLEXER case

Hi, On 7/8/2017 11:59 PM, Peter Rosin wrote: On 2017-07-08 23:22, Andy Shevchenko wrote: On Sat, Jul 8, 2017 at 9:12 PM, wrote: From: Kuppuswamy Sathyanarayanan Add dummy functions to avoid compile

Re: [PATCH v2 1/1] mux: consumer: Add dummy functions for !CONFIG_MULTIPLEXER case

Hi, On 7/8/2017 11:59 PM, Peter Rosin wrote: On 2017-07-08 23:22, Andy Shevchenko wrote: On Sat, Jul 8, 2017 at 9:12 PM, wrote: From: Kuppuswamy Sathyanarayanan Add dummy functions to avoid compile time issues when CONFIG_MULTIPLEXER is not enabled. I don't think the error return code

[PATCH v3] sched/cputime: Fix using smp_processor_id() in preemptible

From: Wanpeng Li BUG: using smp_processor_id() in preemptible [] code: 99-trinity/181 caller is debug_smp_processor_id+0x17/0x19 CPU: 0 PID: 181 Comm: 99-trinity Not tainted 4.12.0-01059-g2a42eb9 #1 Call Trace: dump_stack+0x82/0xb8

[PATCH v3] sched/cputime: Fix using smp_processor_id() in preemptible

From: Wanpeng Li BUG: using smp_processor_id() in preemptible [] code: 99-trinity/181 caller is debug_smp_processor_id+0x17/0x19 CPU: 0 PID: 181 Comm: 99-trinity Not tainted 4.12.0-01059-g2a42eb9 #1 Call Trace: dump_stack+0x82/0xb8 check_preemption_disabled+0xd1/0xe3

Re: [PATCH v2 1/1] mux: mux-core: Add NULL check for dev->of_node

Hi, On 7/9/2017 12:07 AM, Peter Rosin wrote: On 2017-07-09 01:12, Kuppuswamy, Sathyanarayanan wrote: Hi Peter, On 7/8/2017 2:00 PM, Peter Rosin wrote: On 2017-07-07 23:46, sathyanarayanan.kuppusw...@linux.intel.com wrote: From: Kuppuswamy Sathyanarayanan

Re: [PATCH v2 1/1] mux: mux-core: Add NULL check for dev->of_node

Hi, On 7/9/2017 12:07 AM, Peter Rosin wrote: On 2017-07-09 01:12, Kuppuswamy, Sathyanarayanan wrote: Hi Peter, On 7/8/2017 2:00 PM, Peter Rosin wrote: On 2017-07-07 23:46, sathyanarayanan.kuppusw...@linux.intel.com wrote: From: Kuppuswamy Sathyanarayanan If dev->of_node is NULL, then

Re: [RFC PATCH 1/1] mm/mremap: add MREMAP_MIRROR flag for existing mirroring functionality

On 07/07/2017 11:39 PM, Mike Kravetz wrote: > On 07/07/2017 10:45 AM, Kirill A. Shutemov wrote: >> On Fri, Jul 07, 2017 at 10:29:52AM -0700, Mike Kravetz wrote: >>> On 07/07/2017 03:23 AM, Kirill A. Shutemov wrote: On Thu, Jul 06, 2017 at 09:17:26AM -0700, Mike Kravetz wrote: > The mremap

Re: [RFC PATCH 1/1] mm/mremap: add MREMAP_MIRROR flag for existing mirroring functionality

On 07/07/2017 11:39 PM, Mike Kravetz wrote: > On 07/07/2017 10:45 AM, Kirill A. Shutemov wrote: >> On Fri, Jul 07, 2017 at 10:29:52AM -0700, Mike Kravetz wrote: >>> On 07/07/2017 03:23 AM, Kirill A. Shutemov wrote: On Thu, Jul 06, 2017 at 09:17:26AM -0700, Mike Kravetz wrote: > The mremap

RFC: Task switch emulation fails for VM86 mode

Hi all, I found that task switch emulation fails to work for VM86 mode if guest state is invalid. It can be reproduced by running kvm-unit-tests/taskswitch2.flat, EPT = 0 or EPT=1, unrestricted_guest=N, emulate_invalid_guest_state=Y. When EPT=1, unrestricted_guest=Y, emulate_invalid_state=Y, the

RFC: Task switch emulation fails for VM86 mode

Hi all, I found that task switch emulation fails to work for VM86 mode if guest state is invalid. It can be reproduced by running kvm-unit-tests/taskswitch2.flat, EPT = 0 or EPT=1, unrestricted_guest=N, emulate_invalid_guest_state=Y. When EPT=1, unrestricted_guest=Y, emulate_invalid_state=Y, the

Re: [RFC PATCH 1/1] mm/mremap: add MREMAP_MIRROR flag for existing mirroring functionality

On 07/07/2017 10:44 PM, Mike Kravetz wrote: > On 07/07/2017 01:45 AM, Anshuman Khandual wrote: >> On 07/06/2017 09:47 PM, Mike Kravetz wrote: >>> The mremap system call has the ability to 'mirror' parts of an existing >>> mapping. To do so, it creates a new mapping that maps the same pages as >>>

Re: [RFC PATCH 1/1] mm/mremap: add MREMAP_MIRROR flag for existing mirroring functionality

On 07/07/2017 10:44 PM, Mike Kravetz wrote: > On 07/07/2017 01:45 AM, Anshuman Khandual wrote: >> On 07/06/2017 09:47 PM, Mike Kravetz wrote: >>> The mremap system call has the ability to 'mirror' parts of an existing >>> mapping. To do so, it creates a new mapping that maps the same pages as >>>

Re: [PATCH v5 5/5] intel_idle: Add S0ix validation

-pmc-function/20170709-134714 base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next config: x86_64-randconfig-x015-201728 (attached as .config) compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901 reproduce: # save the attached .config to linux build tree

Re: [PATCH v5 5/5] intel_idle: Add S0ix validation

-pmc-function/20170709-134714 base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next config: x86_64-randconfig-x015-201728 (attached as .config) compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901 reproduce: # save the attached .config to linux build tree

Re: [PATCH v2 1/1] mux: mux-core: Add NULL check for dev->of_node

On 2017-07-09 01:12, Kuppuswamy, Sathyanarayanan wrote: > Hi Peter, > > > On 7/8/2017 2:00 PM, Peter Rosin wrote: >> On 2017-07-07 23:46, sathyanarayanan.kuppusw...@linux.intel.com wrote: >>> From: Kuppuswamy Sathyanarayanan >>> >>> >>> If

Re: [PATCH v2 1/1] mux: mux-core: Add NULL check for dev->of_node

On 2017-07-09 01:12, Kuppuswamy, Sathyanarayanan wrote: > Hi Peter, > > > On 7/8/2017 2:00 PM, Peter Rosin wrote: >> On 2017-07-07 23:46, sathyanarayanan.kuppusw...@linux.intel.com wrote: >>> From: Kuppuswamy Sathyanarayanan >>> >>> >>> If dev->of_node is NULL, then calling mux_control_get()

Re: [PATCH] tpm: tpm_crb: constify acpi_device_id.

On Thu, Jul 06, 2017 at 11:18:39PM +0530, Arvind Yadav wrote: > acpi_device_id are not supposed to change at runtime. All functions > working with acpi_device_id provided by work with > const acpi_device_id. So mark the non-const structs as const. > > File size before: >text data

Re: [PATCH] tpm: tpm_crb: constify acpi_device_id.

On Thu, Jul 06, 2017 at 11:18:39PM +0530, Arvind Yadav wrote: > acpi_device_id are not supposed to change at runtime. All functions > working with acpi_device_id provided by work with > const acpi_device_id. So mark the non-const structs as const. > > File size before: >text data

Re: [PATCH v4 RESEND 1/2] Documentation: tpm: add powered-while-suspended binding documentation

On Wed, Jul 05, 2017 at 10:19:02AM -0700, Sonny Rao wrote: > On Mon, Jul 3, 2017 at 5:57 AM, Jarkko Sakkinen > wrote: > > On Tue, Jun 27, 2017 at 12:27:23PM +0200, Enric Balletbo i Serra wrote: > >> Add a new powered-while-suspended property to control the

Re: [PATCH v4 RESEND 1/2] Documentation: tpm: add powered-while-suspended binding documentation

On Wed, Jul 05, 2017 at 10:19:02AM -0700, Sonny Rao wrote: > On Mon, Jul 3, 2017 at 5:57 AM, Jarkko Sakkinen > wrote: > > On Tue, Jun 27, 2017 at 12:27:23PM +0200, Enric Balletbo i Serra wrote: > >> Add a new powered-while-suspended property to control the behavior of the > >> TPM suspend/resume.

Re: [PATCH v2 1/1] mux: consumer: Add dummy functions for !CONFIG_MULTIPLEXER case

On 2017-07-08 23:22, Andy Shevchenko wrote: > On Sat, Jul 8, 2017 at 9:12 PM, > wrote: >> From: Kuppuswamy Sathyanarayanan >> >> Add dummy functions to avoid compile time issues when CONFIG_MULTIPLEXER >> is

Re: [PATCH v2 1/1] mux: consumer: Add dummy functions for !CONFIG_MULTIPLEXER case

On 2017-07-08 23:22, Andy Shevchenko wrote: > On Sat, Jul 8, 2017 at 9:12 PM, > wrote: >> From: Kuppuswamy Sathyanarayanan >> >> Add dummy functions to avoid compile time issues when CONFIG_MULTIPLEXER >> is not enabled. >> > > I don't think the error return code is okay to all of them. The

Re: [PATCH v3 1/1] usb:host:xhci support option to disable the xHCI USB2 HW LPM

On Sun, Jul 09, 2017 at 12:38:19PM +0700, Thang Q. Nguyen wrote: > On Fri, Jun 23, 2017 at 10:02 AM, Thang Q. Nguyen wrote: > > XHCI specification 1.1 does not require xHCI-compliant controllers > > to always enable hardware USB2 LPM. However, the current xHCI > > driver always

Re: [PATCH v3 1/1] usb:host:xhci support option to disable the xHCI USB2 HW LPM

On Sun, Jul 09, 2017 at 12:38:19PM +0700, Thang Q. Nguyen wrote: > On Fri, Jun 23, 2017 at 10:02 AM, Thang Q. Nguyen wrote: > > XHCI specification 1.1 does not require xHCI-compliant controllers > > to always enable hardware USB2 LPM. However, the current xHCI > > driver always enable it when

<    1   2   3   4   5   6