Re: [RESEND PATCH v2 0/5] ir-rx51 driver fixes

* Ivaylo Dimitrov [160622 12:25]: > ir-rx51 is a driver for Nokia N900 IR transmitter. The current series > fixes the remaining problems in the driver: Thanks for updating these. Trierry, care to ack the PWM patch? Mauro, do you want me to set up an immutable

Re: [RESEND PATCH v2 0/5] ir-rx51 driver fixes

* Ivaylo Dimitrov [160622 12:25]: > ir-rx51 is a driver for Nokia N900 IR transmitter. The current series > fixes the remaining problems in the driver: Thanks for updating these. Trierry, care to ack the PWM patch? Mauro, do you want me to set up an immutable branch with all these against

Re: [PATCHv4 1/1] thermal: core: call thermal_zone_device_update() after mode update

On Wednesday 22 June 2016 08:33 PM, Eduardo Valentin wrote: Because several drivers do the following pattern: .set_mode() ... local_data->mode = new_mode; thermal_zone_device_update(tz); makes sense to simply do the thermal_zone_device_update() in thermal core, after setting the

Re: [PATCHv4 1/1] thermal: core: call thermal_zone_device_update() after mode update

On Wednesday 22 June 2016 08:33 PM, Eduardo Valentin wrote: Because several drivers do the following pattern: .set_mode() ... local_data->mode = new_mode; thermal_zone_device_update(tz); makes sense to simply do the thermal_zone_device_update() in thermal core, after setting the

Re: [RFC PATCH 1/4] Documentation: mmc: add description for new caps

Hi, On Wed, Jun 22, 2016 at 6:29 PM, Shawn Lin wrote: > 在 2016/6/22 23:06, Doug Anderson 写道: >> >> Hi, >> >> On Wed, Jun 8, 2016 at 1:20 AM, Shawn Lin >> wrote: >>> >>> Let's add some basic description for cap-no-sdio, >>> cap-no-sd and

Re: [RFC PATCH 1/4] Documentation: mmc: add description for new caps

Hi, On Wed, Jun 22, 2016 at 6:29 PM, Shawn Lin wrote: > 在 2016/6/22 23:06, Doug Anderson 写道: >> >> Hi, >> >> On Wed, Jun 8, 2016 at 1:20 AM, Shawn Lin >> wrote: >>> >>> Let's add some basic description for cap-no-sdio, >>> cap-no-sd and cap-no-mmc. >>> >>> Signed-off-by: Shawn Lin >>> >>> ---

Re: [PATCH 01/27] [AARCH64] Fix utmp struct for compatibility reasons.

On Tue, Jun 21, 2016 at 11:14:54AM +0100, Szabolcs Nagy wrote: > On 21/06/16 06:06, Yury Norov wrote: > > From: Andrew Pinski > > > > NOTE This is an ABI change for AARCH64. > > If you have some AARCH32 and AARCH64 applications and they both use > > utmp, one of them will

Re: [PATCH 01/27] [AARCH64] Fix utmp struct for compatibility reasons.

On Tue, Jun 21, 2016 at 11:14:54AM +0100, Szabolcs Nagy wrote: > On 21/06/16 06:06, Yury Norov wrote: > > From: Andrew Pinski > > > > NOTE This is an ABI change for AARCH64. > > If you have some AARCH32 and AARCH64 applications and they both use > > utmp, one of them will fail due to the use of

Re: 4.7 regression - ACPICA: Hardware: Enhance acpi_hw_validate_register() with access_width/bit_offset awareness

On Thu, 2016-06-23 at 00:32 +, Zheng, Lv wrote: > Could you try to boot it with one of the following parameters or both of the > parameters: > acpi=rsdt > Or > acpi_force_32bit_fadt_addr Box was unimpressed by either or both. > Please also send us the acpidump/dmidecode outputs for

Re: 4.7 regression - ACPICA: Hardware: Enhance acpi_hw_validate_register() with access_width/bit_offset awareness

On Thu, 2016-06-23 at 00:32 +, Zheng, Lv wrote: > Could you try to boot it with one of the following parameters or both of the > parameters: > acpi=rsdt > Or > acpi_force_32bit_fadt_addr Box was unimpressed by either or both. > Please also send us the acpidump/dmidecode outputs for

linux-next: manual merge of the audit tree with the security tree

Hi Paul, Today's linux-next merge of the audit tree got a conflict in: arch/s390/kernel/ptrace.c between commit: 0208b9445bc0 ("s390/ptrace: run seccomp after ptrace") from the security tree and commit: bba696c2c083 ("s390: ensure that syscall arguments are properly masked on s390")

linux-next: manual merge of the audit tree with the security tree

Hi Paul, Today's linux-next merge of the audit tree got a conflict in: arch/s390/kernel/ptrace.c between commit: 0208b9445bc0 ("s390/ptrace: run seccomp after ptrace") from the security tree and commit: bba696c2c083 ("s390: ensure that syscall arguments are properly masked on s390")

Re: [RFC PATCH 1/2] drm: bridge: anx7688: Add anx7688 bridge driver support.

Hi Philipp, On Wed, Jun 22, 2016 at 4:51 PM, Philipp Zabel wrote: > Hi Nicolas, > > Am Mittwoch, den 22.06.2016, 14:32 +0800 schrieb Nicolas Boichat: >> >> Actually, experimenting a bit more with the code, I realized that the >> >> connector is always attached to the

Re: [RFC PATCH 1/2] drm: bridge: anx7688: Add anx7688 bridge driver support.

Hi Philipp, On Wed, Jun 22, 2016 at 4:51 PM, Philipp Zabel wrote: > Hi Nicolas, > > Am Mittwoch, den 22.06.2016, 14:32 +0800 schrieb Nicolas Boichat: >> >> Actually, experimenting a bit more with the code, I realized that the >> >> connector is always attached to the encoder, not the bridge, so

Re: kernel-4.7 bug in Intel sound and/or ACPI

On 2016-06-21 18:13, Wim Osterholt wrote: On Tue, Jun 21, 2016 at 09:40:10AM -0400, Sinan Kaya wrote: Thanks, It was a guess with no proof. Let's undo the change above and start adding some print statements to collect data from your system. Can you add this to the end of

Re: kernel-4.7 bug in Intel sound and/or ACPI

On 2016-06-21 18:13, Wim Osterholt wrote: On Tue, Jun 21, 2016 at 09:40:10AM -0400, Sinan Kaya wrote: Thanks, It was a guess with no proof. Let's undo the change above and start adding some print statements to collect data from your system. Can you add this to the end of

Re: Doing crypto in small stack buffers (bluetooth vs vmalloc-stack crash, etc)

On Wed, Jun 22, 2016 at 04:45:46PM -0700, Andy Lutomirski wrote: > > *However*, the other offender I've found (net/rxrpc/rxkad.c) uses > "pcbc(fcrypt)", which doesn't appear to be usable with this API. Is > there no way to say "I want synchronous crypto on this VA range" using > the skcipher API?

Re: Doing crypto in small stack buffers (bluetooth vs vmalloc-stack crash, etc)

On Wed, Jun 22, 2016 at 04:45:46PM -0700, Andy Lutomirski wrote: > > *However*, the other offender I've found (net/rxrpc/rxkad.c) uses > "pcbc(fcrypt)", which doesn't appear to be usable with this API. Is > there no way to say "I want synchronous crypto on this VA range" using > the skcipher API?

Re: Doing crypto in small stack buffers (bluetooth vs vmalloc-stack crash, etc)

On Wed, Jun 22, 2016 at 02:48:24PM -0700, Andy Lutomirski wrote: > > Before I do this, can you explain what the difference is between > crypto_cipher and crypto_skcipher? net/bluetooth/smp.c currently uses > crypto_alloc_skcipher, which you added in: crypto_cipher operates on a single block.

Re: Doing crypto in small stack buffers (bluetooth vs vmalloc-stack crash, etc)

On Wed, Jun 22, 2016 at 02:48:24PM -0700, Andy Lutomirski wrote: > > Before I do this, can you explain what the difference is between > crypto_cipher and crypto_skcipher? net/bluetooth/smp.c currently uses > crypto_alloc_skcipher, which you added in: crypto_cipher operates on a single block.

Re: [PATCH 2/2] sparc64: Fix pagetable freeing for hugepage regions

Hi, [auto build test ERROR on sparc/master] [also build test ERROR on v4.7-rc4 next-20160622] [cannot apply to sparc-next/master] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Nitin-Gupta

Re: [PATCH 2/2] sparc64: Fix pagetable freeing for hugepage regions

Hi, [auto build test ERROR on sparc/master] [also build test ERROR on v4.7-rc4 next-20160622] [cannot apply to sparc-next/master] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Nitin-Gupta

Re: [PATCH] Maxim/driver: Add driver for maxim ds26522

Hi, [auto build test ERROR on net-next/master] [also build test ERROR on next-20160622] [cannot apply to v4.7-rc4] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Zhao-Qiang/Maxim-driver-Add

Re: [PATCH] Maxim/driver: Add driver for maxim ds26522

Hi, [auto build test ERROR on net-next/master] [also build test ERROR on next-20160622] [cannot apply to v4.7-rc4] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Zhao-Qiang/Maxim-driver-Add

Re: [PATCH 2/2] sparc64: Fix pagetable freeing for hugepage regions

Hi, [auto build test ERROR on sparc/master] [also build test ERROR on v4.7-rc4 next-20160622] [cannot apply to sparc-next/master] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Nitin-Gupta

Re: [PATCH 2/2] sparc64: Fix pagetable freeing for hugepage regions

Hi, [auto build test ERROR on sparc/master] [also build test ERROR on v4.7-rc4 next-20160622] [cannot apply to sparc-next/master] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Nitin-Gupta

Re: [PATCH] config: Add android config fragments

On Wed, Jun 22, 2016 at 2:53 AM, Amit Pundir wrote: > On 8 June 2016 at 22:09, Rob Herring wrote: >> Copy the config fragments from the AOSP common kernel tree. It is >> becoming possible to run mainline kernels with Android, but the kernel >> defconfigs

Re: [PATCH] config: Add android config fragments

On Wed, Jun 22, 2016 at 2:53 AM, Amit Pundir wrote: > On 8 June 2016 at 22:09, Rob Herring wrote: >> Copy the config fragments from the AOSP common kernel tree. It is >> becoming possible to run mainline kernels with Android, but the kernel >> defconfigs don't work as-is and debugging missing

Re: [PATCH 5/5] perf tools: Fix NULL pointer deference when vdso not found

在 2016/6/23 10:02, Wangnan (F) 写道: Hi, This patch fixes a real crash problem when we do 'perf report' on an arm64 platform with arm32 program. It is introduced by commit f9b2bdf228 ("perf tools: Find vdso with the consider of cross-platform"). From dmesg report, perf crashes in dso__type()

Re: [PATCH 5/5] perf tools: Fix NULL pointer deference when vdso not found

在 2016/6/23 10:02, Wangnan (F) 写道: Hi, This patch fixes a real crash problem when we do 'perf report' on an arm64 platform with arm32 program. It is introduced by commit f9b2bdf228 ("perf tools: Find vdso with the consider of cross-platform"). From dmesg report, perf crashes in dso__type()

linux-next: manual merge of the sunxi tree with the drm-misc tree

Hi Maxime, Today's linux-next merge of the sunxi tree got a conflict in: drivers/gpu/drm/sun4i/sun4i_drv.c between commit: 366e292df678 ("drm/sun4i: Remove open-coded drm_connector_register_all()") from the drm-misc tree and commit: 7aa2e2b731b3 ("drm/sun4i: Convert to connector

linux-next: manual merge of the sunxi tree with the drm-misc tree

Hi Maxime, Today's linux-next merge of the sunxi tree got a conflict in: drivers/gpu/drm/sun4i/sun4i_drv.c between commit: 366e292df678 ("drm/sun4i: Remove open-coded drm_connector_register_all()") from the drm-misc tree and commit: 7aa2e2b731b3 ("drm/sun4i: Convert to connector

Re: [PATCH v4] vfio-pci: Allow to mmap sub-page MMIO BARs if the mmio page is exclusive

On Thu, 23 Jun 2016 10:39:30 +0800 Yongji Xie wrote: > Hi, Alex > > On 2016/6/23 6:04, Alex Williamson wrote: > > > On Mon, 30 May 2016 21:06:37 +0800 > > Yongji Xie wrote: > > > >> Current vfio-pci implementation disallows to mmap > >>

Re: [PATCH v4] vfio-pci: Allow to mmap sub-page MMIO BARs if the mmio page is exclusive

On Thu, 23 Jun 2016 10:39:30 +0800 Yongji Xie wrote: > Hi, Alex > > On 2016/6/23 6:04, Alex Williamson wrote: > > > On Mon, 30 May 2016 21:06:37 +0800 > > Yongji Xie wrote: > > > >> Current vfio-pci implementation disallows to mmap > >> sub-page(size < PAGE_SIZE) MMIO BARs because these

Re: Boot failure on emev2/kzm9d (was: Re: [PATCH v2 11/11] mm/slab: lockless decision to grow cache)

On Wed, Jun 22, 2016 at 07:47:42PM -0700, Paul E. McKenney wrote: > On Thu, Jun 23, 2016 at 11:37:56AM +0900, Joonsoo Kim wrote: > > On Wed, Jun 22, 2016 at 05:49:35PM -0700, Paul E. McKenney wrote: > > > On Wed, Jun 22, 2016 at 12:08:59PM -0700, Paul E. McKenney wrote: > > > > On Wed, Jun 22,

Re: Boot failure on emev2/kzm9d (was: Re: [PATCH v2 11/11] mm/slab: lockless decision to grow cache)

On Wed, Jun 22, 2016 at 07:47:42PM -0700, Paul E. McKenney wrote: > On Thu, Jun 23, 2016 at 11:37:56AM +0900, Joonsoo Kim wrote: > > On Wed, Jun 22, 2016 at 05:49:35PM -0700, Paul E. McKenney wrote: > > > On Wed, Jun 22, 2016 at 12:08:59PM -0700, Paul E. McKenney wrote: > > > > On Wed, Jun 22,

Re: [PATCH v3 3/6] mm/cma: populate ZONE_CMA

On Wed, Jun 22, 2016 at 05:23:06PM +0800, Chen Feng wrote: > Hello, > > On 2016/5/26 14:22, js1...@gmail.com wrote: > > From: Joonsoo Kim > > > > Until now, reserved pages for CMA are managed in the ordinary zones > > where page's pfn are belong to. This approach has

Re: [PATCH v3 3/6] mm/cma: populate ZONE_CMA

On Wed, Jun 22, 2016 at 05:23:06PM +0800, Chen Feng wrote: > Hello, > > On 2016/5/26 14:22, js1...@gmail.com wrote: > > From: Joonsoo Kim > > > > Until now, reserved pages for CMA are managed in the ordinary zones > > where page's pfn are belong to. This approach has numorous problems > > and

Re: Boot failure on emev2/kzm9d (was: Re: [PATCH v2 11/11] mm/slab: lockless decision to grow cache)

On Thu, Jun 23, 2016 at 11:37:56AM +0900, Joonsoo Kim wrote: > On Wed, Jun 22, 2016 at 05:49:35PM -0700, Paul E. McKenney wrote: > > On Wed, Jun 22, 2016 at 12:08:59PM -0700, Paul E. McKenney wrote: > > > On Wed, Jun 22, 2016 at 05:01:35PM +0200, Geert Uytterhoeven wrote: > > > > On Wed, Jun 22,

Re: Boot failure on emev2/kzm9d (was: Re: [PATCH v2 11/11] mm/slab: lockless decision to grow cache)

On Thu, Jun 23, 2016 at 11:37:56AM +0900, Joonsoo Kim wrote: > On Wed, Jun 22, 2016 at 05:49:35PM -0700, Paul E. McKenney wrote: > > On Wed, Jun 22, 2016 at 12:08:59PM -0700, Paul E. McKenney wrote: > > > On Wed, Jun 22, 2016 at 05:01:35PM +0200, Geert Uytterhoeven wrote: > > > > On Wed, Jun 22,

RE: [PATCH 2/4] soc: fsl: add GUTS driver for QorIQ platforms

Hi Arnd, Could you comment on these? Thanks. Best regards, Yangbo Lu > -Original Message- > From: Scott Wood [mailto:o...@buserror.net] > Sent: Saturday, June 11, 2016 9:51 AM > To: Arnd Bergmann; linuxppc-...@lists.ozlabs.org > Cc: Mark Rutland; Ulf Hansson;

RE: [PATCH 2/4] soc: fsl: add GUTS driver for QorIQ platforms

Hi Arnd, Could you comment on these? Thanks. Best regards, Yangbo Lu > -Original Message- > From: Scott Wood [mailto:o...@buserror.net] > Sent: Saturday, June 11, 2016 9:51 AM > To: Arnd Bergmann; linuxppc-...@lists.ozlabs.org > Cc: Mark Rutland; Ulf Hansson;

Re: [PATCH v4] vfio-pci: Allow to mmap sub-page MMIO BARs if the mmio page is exclusive

Hi, Alex On 2016/6/23 6:04, Alex Williamson wrote: On Mon, 30 May 2016 21:06:37 +0800 Yongji Xie wrote: Current vfio-pci implementation disallows to mmap sub-page(size < PAGE_SIZE) MMIO BARs because these BARs' mmio page may be shared with other BARs. This will

Re: [PATCH v4] vfio-pci: Allow to mmap sub-page MMIO BARs if the mmio page is exclusive

Hi, Alex On 2016/6/23 6:04, Alex Williamson wrote: On Mon, 30 May 2016 21:06:37 +0800 Yongji Xie wrote: Current vfio-pci implementation disallows to mmap sub-page(size < PAGE_SIZE) MMIO BARs because these BARs' mmio page may be shared with other BARs. This will cause some performance issues

Re: [PATCH 2/2] sparc64: Fix pagetable freeing for hugepage regions

Hi, [auto build test ERROR on sparc/master] [also build test ERROR on v4.7-rc4 next-20160622] [cannot apply to sparc-next/master] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Nitin-Gupta

Re: Boot failure on emev2/kzm9d (was: Re: [PATCH v2 11/11] mm/slab: lockless decision to grow cache)

On Wed, Jun 22, 2016 at 05:49:35PM -0700, Paul E. McKenney wrote: > On Wed, Jun 22, 2016 at 12:08:59PM -0700, Paul E. McKenney wrote: > > On Wed, Jun 22, 2016 at 05:01:35PM +0200, Geert Uytterhoeven wrote: > > > On Wed, Jun 22, 2016 at 2:52 AM, Joonsoo Kim > > > wrote: >

Re: [PATCH 2/2] sparc64: Fix pagetable freeing for hugepage regions

Hi, [auto build test ERROR on sparc/master] [also build test ERROR on v4.7-rc4 next-20160622] [cannot apply to sparc-next/master] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Nitin-Gupta

Re: Boot failure on emev2/kzm9d (was: Re: [PATCH v2 11/11] mm/slab: lockless decision to grow cache)

On Wed, Jun 22, 2016 at 05:49:35PM -0700, Paul E. McKenney wrote: > On Wed, Jun 22, 2016 at 12:08:59PM -0700, Paul E. McKenney wrote: > > On Wed, Jun 22, 2016 at 05:01:35PM +0200, Geert Uytterhoeven wrote: > > > On Wed, Jun 22, 2016 at 2:52 AM, Joonsoo Kim > > > wrote: > > > > Could you try

Re: adf_ctl_drv.c:(.init.text+0x14915): undefined reference to `adf_init_pf_wq' (was Linux 4.4.13)

On Wed, Jun 22, 2016 at 05:52:28PM -0700, Randy Dunlap wrote: > On 06/22/16 17:37, Greg KH wrote: > > On Wed, Jun 22, 2016 at 04:41:07PM -0700, Randy Dunlap wrote: > >> On 06/22/16 03:49, Hans de Bruin wrote: > >>> On 06/20/2016 07:17 PM, Randy Dunlap wrote: > On 06/20/16 08:43, Greg KH

Re: adf_ctl_drv.c:(.init.text+0x14915): undefined reference to `adf_init_pf_wq' (was Linux 4.4.13)

On Wed, Jun 22, 2016 at 05:52:28PM -0700, Randy Dunlap wrote: > On 06/22/16 17:37, Greg KH wrote: > > On Wed, Jun 22, 2016 at 04:41:07PM -0700, Randy Dunlap wrote: > >> On 06/22/16 03:49, Hans de Bruin wrote: > >>> On 06/20/2016 07:17 PM, Randy Dunlap wrote: > On 06/20/16 08:43, Greg KH

Re: [PATCH v3 3/9] kexec_file: Factor out kexec_locate_mem_hole from kexec_add_buffer.

On 06/22/16 at 08:34pm, Thiago Jung Bauermann wrote: > Am Mittwoch, 22 Juni 2016, 18:18:01 schrieb Dave Young: > > On 06/21/16 at 04:48pm, Thiago Jung Bauermann wrote: > > > +/** > > > + * kexec_locate_mem_hole - find free memory to load segment or use in > > > purgatory + * @image: kexec

Re: [PATCH v3 3/9] kexec_file: Factor out kexec_locate_mem_hole from kexec_add_buffer.

On 06/22/16 at 08:34pm, Thiago Jung Bauermann wrote: > Am Mittwoch, 22 Juni 2016, 18:18:01 schrieb Dave Young: > > On 06/21/16 at 04:48pm, Thiago Jung Bauermann wrote: > > > +/** > > > + * kexec_locate_mem_hole - find free memory to load segment or use in > > > purgatory + * @image: kexec

[PATCH 2/5] nohz,cputime: remove VTIME_GEN vtime irq time code

From: Rik van Riel The CONFIG_VIRT_CPU_ACCOUNTING_GEN irq time tracking code does not appear to currently work right. On CPUs that are nohz_full, people typically do not assign IRQs. On the housekeeping CPU (when a system is booted up with nohz_full), sampling should work ok to

[PATCH 2/5] nohz,cputime: remove VTIME_GEN vtime irq time code

From: Rik van Riel The CONFIG_VIRT_CPU_ACCOUNTING_GEN irq time tracking code does not appear to currently work right. On CPUs that are nohz_full, people typically do not assign IRQs. On the housekeeping CPU (when a system is booted up with nohz_full), sampling should work ok to determine irq

[PATCH 1/5] sched,time: count actually elapsed irq & softirq time

From: Rik van Riel Currently, if there was any irq or softirq time during 'ticks' jiffies, the entire period will be accounted as irq or softirq time. This is inaccurate if only a subset of 'ticks' jiffies was actually spent handling irqs, and could conceivably mis-count all of

[PATCH 3/5] cputime: allow irq time accounting to be selected as an option

From: Rik van Riel Allow CONFIG_IRQ_TIME_ACCOUNTING to be selected as an option, on top of CONFIG_VIRT_CPU_ACCOUNTING_GEN (and potentially others?). This allows for the irq time accounting code to be used with nohz_idle CPUs, which is how several distributions ship their

[PATCH 4/5] irqtime: add irq type parameter to irqtime_account_irq

From: Rik van Riel Add an irq type parameter and documentation to irqtime_account_irq, this can be used to distinguish between transitioning from process context to hardirq time, and from process context to softirq time. This is necessary to be able to remove the

[PATCH 1/5] sched,time: count actually elapsed irq & softirq time

From: Rik van Riel Currently, if there was any irq or softirq time during 'ticks' jiffies, the entire period will be accounted as irq or softirq time. This is inaccurate if only a subset of 'ticks' jiffies was actually spent handling irqs, and could conceivably mis-count all of the ticks during

[PATCH 3/5] cputime: allow irq time accounting to be selected as an option

From: Rik van Riel Allow CONFIG_IRQ_TIME_ACCOUNTING to be selected as an option, on top of CONFIG_VIRT_CPU_ACCOUNTING_GEN (and potentially others?). This allows for the irq time accounting code to be used with nohz_idle CPUs, which is how several distributions ship their kernels. Using the same

[PATCH 4/5] irqtime: add irq type parameter to irqtime_account_irq

From: Rik van Riel Add an irq type parameter and documentation to irqtime_account_irq, this can be used to distinguish between transitioning from process context to hardirq time, and from process context to softirq time. This is necessary to be able to remove the local_irq_disable from

[PATCH 5/5] irqtime: drop local_irq_save/restore from irqtime_account_irq

From: Rik van Riel Drop local_irq_save/restore from irqtime_account_irq. Instead, have softirq and hardirq track their time spent independently, with the softirq code subtracting hardirq time that happened during the duration of the softirq run. The softirq code can be

[PATCH 5/5] irqtime: drop local_irq_save/restore from irqtime_account_irq

From: Rik van Riel Drop local_irq_save/restore from irqtime_account_irq. Instead, have softirq and hardirq track their time spent independently, with the softirq code subtracting hardirq time that happened during the duration of the softirq run. The softirq code can be interrupted by hardirq

[PATCH v2 0/5] sched,time: fix irq time accounting with nohz_idle

Currently irq time accounting only works in these cases: 1) purely ticke based accounting 2) nohz_full accounting, but only on housekeeping & nohz_full CPUs 3) architectures with native vtime accounting On nohz_idle CPUs, which are probably the majority nowadays, irq time accounting is currently

[PATCH v2 0/5] sched,time: fix irq time accounting with nohz_idle

Currently irq time accounting only works in these cases: 1) purely ticke based accounting 2) nohz_full accounting, but only on housekeeping & nohz_full CPUs 3) architectures with native vtime accounting On nohz_idle CPUs, which are probably the majority nowadays, irq time accounting is currently

Re: [PATCH v3 2/9] kexec_file: Generalize kexec_add_buffer.

On 06/22/16 at 08:30pm, Thiago Jung Bauermann wrote: > Am Mittwoch, 22 Juni 2016, 18:20:47 schrieb Dave Young: > > The patch looks good, but could the subject be more specific? > > > > For example just like the first sentence of the patch descriotion: > > Allow architectures to specify their own

Re: [PATCH v3 2/9] kexec_file: Generalize kexec_add_buffer.

On 06/22/16 at 08:30pm, Thiago Jung Bauermann wrote: > Am Mittwoch, 22 Juni 2016, 18:20:47 schrieb Dave Young: > > The patch looks good, but could the subject be more specific? > > > > For example just like the first sentence of the patch descriotion: > > Allow architectures to specify their own

[PATCH] PM / devfreq: Send the DEVFREQ_POSTCHANGE notification when target() is failed

This patch sends the DEVFREQ_POSTCHANGE notification when devfreq->profile->targer() is failed. The PRECHANGE/POSTCHANGE should be paired. Fixes: 0fe3a66410a3 ("PM / devfreq: Add new DEVFREQ_TRANSITION_NOTIFIER notifier") Reported-by: Lin Huang Signed-off-by: Chanwoo Choi

[PATCH] PM / devfreq: Send the DEVFREQ_POSTCHANGE notification when target() is failed

This patch sends the DEVFREQ_POSTCHANGE notification when devfreq->profile->targer() is failed. The PRECHANGE/POSTCHANGE should be paired. Fixes: 0fe3a66410a3 ("PM / devfreq: Add new DEVFREQ_TRANSITION_NOTIFIER notifier") Reported-by: Lin Huang Signed-off-by: Chanwoo Choi ---

Re: [PATCH v3 2/2] PCI: Rockchip: Add Rockchip PCIe controller support

在 2016/6/23 9:35, Brian Norris 写道: Hi, On Thu, Jun 23, 2016 at 09:09:46AM +0800, Shawn Lin wrote: 在 2016/6/23 8:29, Brian Norris 写道: On Thu, Jun 16, 2016 at 09:50:35AM +0800, Shawn Lin wrote: [...] + /* 500ms timeout value should be enough for gen1/2 taining */ + timeout =

Re: [PATCH v3 2/2] PCI: Rockchip: Add Rockchip PCIe controller support

在 2016/6/23 9:35, Brian Norris 写道: Hi, On Thu, Jun 23, 2016 at 09:09:46AM +0800, Shawn Lin wrote: 在 2016/6/23 8:29, Brian Norris 写道: On Thu, Jun 16, 2016 at 09:50:35AM +0800, Shawn Lin wrote: [...] + /* 500ms timeout value should be enough for gen1/2 taining */ + timeout =

[PATCH v9.1] perf evlist: Introduce aux evlist

An auxiliary evlist is created by perf_evlist__new_aux() using an existing evlist as its parent. An auxiliary evlist can have its own 'struct perf_mmap', but can't have any other data. User should use its parent instead when accessing other data. Auxiliary evlists are containers of 'struct

[PATCH v9.1] perf evlist: Introduce aux evlist

An auxiliary evlist is created by perf_evlist__new_aux() using an existing evlist as its parent. An auxiliary evlist can have its own 'struct perf_mmap', but can't have any other data. User should use its parent instead when accessing other data. Auxiliary evlists are containers of 'struct

Re: [PATCH] mmc: core: add auto bkops support

在 2016/6/22 18:21, Ulf Hansson 写道: On 13 June 2016 at 14:25, Adrian Hunter wrote: On 13/06/16 11:58, Shawn Lin wrote: 在 2016/6/13 16:17, Adrian Hunter 写道: On 13/06/16 10:48, Shawn Lin wrote: On 2016/6/13 14:29, Adrian Hunter wrote: On 06/06/16 06:07, Shawn Lin

Re: [PATCH] mmc: core: add auto bkops support

在 2016/6/22 18:21, Ulf Hansson 写道: On 13 June 2016 at 14:25, Adrian Hunter wrote: On 13/06/16 11:58, Shawn Lin wrote: 在 2016/6/13 16:17, Adrian Hunter 写道: On 13/06/16 10:48, Shawn Lin wrote: On 2016/6/13 14:29, Adrian Hunter wrote: On 06/06/16 06:07, Shawn Lin wrote: JEDEC eMMC v5.1

Re: [PATCH 5/5] perf tools: Fix NULL pointer deference when vdso not found

Hi, This patch fixes a real crash problem when we do 'perf report' on an arm64 platform with arm32 program. It is introduced by commit f9b2bdf228 ("perf tools: Find vdso with the consider of cross-platform"). From dmesg report, perf crashes in dso__type() because dso is NULL. Still don't know

Re: [PATCH 5/5] perf tools: Fix NULL pointer deference when vdso not found

Hi, This patch fixes a real crash problem when we do 'perf report' on an arm64 platform with arm32 program. It is introduced by commit f9b2bdf228 ("perf tools: Find vdso with the consider of cross-platform"). From dmesg report, perf crashes in dso__type() because dso is NULL. Still don't know

Re: [Y2038] [PATCH v2 09/24] fs: udf: Replace CURRENT_TIME with current_time()

On Wed, Jun 22, 2016 at 6:54 AM, Arnd Bergmann wrote: > On Sunday, June 19, 2016 5:27:08 PM CEST Deepa Dinamani wrote: >> mutex_lock(>s_alloc_mutex); >> lvidiu->impIdent.identSuffix[0] = UDF_OS_CLASS_UNIX; >> lvidiu->impIdent.identSuffix[1] =

Re: [Y2038] [PATCH v2 09/24] fs: udf: Replace CURRENT_TIME with current_time()

On Wed, Jun 22, 2016 at 6:54 AM, Arnd Bergmann wrote: > On Sunday, June 19, 2016 5:27:08 PM CEST Deepa Dinamani wrote: >> mutex_lock(>s_alloc_mutex); >> lvidiu->impIdent.identSuffix[0] = UDF_OS_CLASS_UNIX; >> lvidiu->impIdent.identSuffix[1] = UDF_OS_ID_LINUX; >> +

[PATCH v4.1 1/2] drm/rockchip: analogix_dp: introduce the pclk for grf

For RK3399's GRF module, if we want to operate the graphic related grf registers, we need to enable the pclk_vio_grf which supply power for VIO GRF IOs, so it's better to introduce an optional grf clock in driver. Signed-off-by: Yakir Yang --- Hi all, This is an external

[PATCH v4.1 1/2] drm/rockchip: analogix_dp: introduce the pclk for grf

For RK3399's GRF module, if we want to operate the graphic related grf registers, we need to enable the pclk_vio_grf which supply power for VIO GRF IOs, so it's better to introduce an optional grf clock in driver. Signed-off-by: Yakir Yang --- Hi all, This is an external patch for analogix_dp

Re: [PATCH V4 1/1] net: ethernet: Add TSE PCS support to dwmac-socfpga

Hi Peppe, On Wed, 2016-06-22 at 11:00 +0200, Giuseppe CAVALLARO wrote: > Hello Tien Hock > > On 6/21/2016 10:46 AM, th...@altera.com wrote: > > From: Tien Hock Loh > > > > This adds support for TSE PCS that uses SGMII adapter when the phy-mode of > > the dwmac is set to sgmii

Re: [PATCH V4 1/1] net: ethernet: Add TSE PCS support to dwmac-socfpga

Hi Peppe, On Wed, 2016-06-22 at 11:00 +0200, Giuseppe CAVALLARO wrote: > Hello Tien Hock > > On 6/21/2016 10:46 AM, th...@altera.com wrote: > > From: Tien Hock Loh > > > > This adds support for TSE PCS that uses SGMII adapter when the phy-mode of > > the dwmac is set to sgmii > > > >

linux-next: build warning after merge of the pci tree

Hi Bjorn, After merging the pci tree, today's linux-next build (x86_64 allmodconfig) produced this warning: drivers/misc/genwqe/card_base.c: In function 'genwqe_pci_remove': drivers/misc/genwqe/card_base.c:1155:6: warning: unused variable 'bars' [-Wunused-variable] int bars; ^

linux-next: build warning after merge of the pci tree

Hi Bjorn, After merging the pci tree, today's linux-next build (x86_64 allmodconfig) produced this warning: drivers/misc/genwqe/card_base.c: In function 'genwqe_pci_remove': drivers/misc/genwqe/card_base.c:1155:6: warning: unused variable 'bars' [-Wunused-variable] int bars; ^

Re: [PATCH v2 19/24] fnic: Use time64_t to represent trace timestamps

On Wed, Jun 22, 2016 at 7:09 AM, Arnd Bergmann wrote: > On Sunday, June 19, 2016 5:27:18 PM CEST Deepa Dinamani wrote: >> trace timestamps use struct timespec and CURRENT_TIME which >> are not y2038 safe. >> These timestamps are only part of the trace log on the machine >> and are

Re: [PATCH v2 19/24] fnic: Use time64_t to represent trace timestamps

On Wed, Jun 22, 2016 at 7:09 AM, Arnd Bergmann wrote: > On Sunday, June 19, 2016 5:27:18 PM CEST Deepa Dinamani wrote: >> trace timestamps use struct timespec and CURRENT_TIME which >> are not y2038 safe. >> These timestamps are only part of the trace log on the machine >> and are not shared with

[PATCH v4 2/2] dt-bindings: analogix_dp: rockchip: correct the wrong compatible name

The document about rockchip platform make a mistaken in available compatible name of "rk3288-edp", we should correct it to "rk3288-dp" which correspond to the compatible name in driver. This mistaken was introduced in commit be91c36247089 ("dt-bindings: add document for rockchip variant of

[PATCH v4 1/2] drm/rockchip: analogix_dp: introduce the pclk for grf

For RK3399's GRF module, if we want to operate the graphic related grf registers, we need to enable the pclk_vio_grf which supply power for VIO GRF IOs, so it's better to introduce an optional grf clock in driver. Signed-off-by: Yakir Yang --- Hi all, This is an external

[PATCH v4 2/2] dt-bindings: analogix_dp: rockchip: correct the wrong compatible name

The document about rockchip platform make a mistaken in available compatible name of "rk3288-edp", we should correct it to "rk3288-dp" which correspond to the compatible name in driver. This mistaken was introduced in commit be91c36247089 ("dt-bindings: add document for rockchip variant of

[PATCH v4 1/2] drm/rockchip: analogix_dp: introduce the pclk for grf

For RK3399's GRF module, if we want to operate the graphic related grf registers, we need to enable the pclk_vio_grf which supply power for VIO GRF IOs, so it's better to introduce an optional grf clock in driver. Signed-off-by: Yakir Yang --- Hi all, This is an external patch for analogix_dp

linux-next: manual merge of the pci tree with Linus' tree

Hi Bjorn, Today's linux-next merge of the pci tree got a conflict in: drivers/nvme/host/pci.c between commit: edb50a5403d2 ("NVMe: Only release requested regions") from Linus' tree and commit: a1f447b35b72 ("NVMe: Use pci_(request|release)_mem_regions") from the pci tree. I fixed it

linux-next: manual merge of the pci tree with Linus' tree

Hi Bjorn, Today's linux-next merge of the pci tree got a conflict in: drivers/nvme/host/pci.c between commit: edb50a5403d2 ("NVMe: Only release requested regions") from Linus' tree and commit: a1f447b35b72 ("NVMe: Use pci_(request|release)_mem_regions") from the pci tree. I fixed it

Re: [PATCH V7 1/8] ACPI: I/O Remapping Table (IORT) initial support

On 2016/6/22 22:51, Marc Zyngier wrote: > On 22/06/16 14:52, Tomasz Nowicki wrote: >> On 22.06.2016 15:25, Marc Zyngier wrote: >>> On 22/06/16 13:35, Tomasz Nowicki wrote: IORT shows representation of IO topology for ARM based systems. It describes how various components are connected

Re: [PATCH V7 1/8] ACPI: I/O Remapping Table (IORT) initial support

On 2016/6/22 22:51, Marc Zyngier wrote: > On 22/06/16 14:52, Tomasz Nowicki wrote: >> On 22.06.2016 15:25, Marc Zyngier wrote: >>> On 22/06/16 13:35, Tomasz Nowicki wrote: IORT shows representation of IO topology for ARM based systems. It describes how various components are connected

[PATCH] Maxim/driver: Add driver for maxim ds26522

Signed-off-by: Zhao Qiang --- drivers/net/wan/Kconfig| 10 ++ drivers/net/wan/Makefile | 1 + drivers/net/wan/slic_ds26522.c | 256 + drivers/net/wan/slic_ds26522.h | 134 + 4 files changed, 401

[PATCH] Maxim/driver: Add driver for maxim ds26522

Signed-off-by: Zhao Qiang --- drivers/net/wan/Kconfig| 10 ++ drivers/net/wan/Makefile | 1 + drivers/net/wan/slic_ds26522.c | 256 + drivers/net/wan/slic_ds26522.h | 134 + 4 files changed, 401 insertions(+) create

Re: [RFC PATCH 0/4] Introduce new caps to improve the card's init sequence

在 2016/6/22 20:37, Ulf Hansson 写道: On 8 June 2016 at 10:19, Shawn Lin wrote: Hi all, This patchset is gonna improve the card's init sequence by exposing some caps to DT. The basic idea is to skip sending specific init cmd inspired by Carlo Caione's commit[0]. To

Re: [PATCH v3 2/2] PCI: Rockchip: Add Rockchip PCIe controller support

Hi, On Thu, Jun 23, 2016 at 09:09:46AM +0800, Shawn Lin wrote: > 在 2016/6/23 8:29, Brian Norris 写道: > >On Thu, Jun 16, 2016 at 09:50:35AM +0800, Shawn Lin wrote: [...] > >>+ /* 500ms timeout value should be enough for gen1/2 taining */ > >>+ timeout = jiffies + msecs_to_jiffies(500); > >>+

Re: [RFC PATCH 0/4] Introduce new caps to improve the card's init sequence

在 2016/6/22 20:37, Ulf Hansson 写道: On 8 June 2016 at 10:19, Shawn Lin wrote: Hi all, This patchset is gonna improve the card's init sequence by exposing some caps to DT. The basic idea is to skip sending specific init cmd inspired by Carlo Caione's commit[0]. To make it possible, I firstly

Re: [PATCH v3 2/2] PCI: Rockchip: Add Rockchip PCIe controller support

Hi, On Thu, Jun 23, 2016 at 09:09:46AM +0800, Shawn Lin wrote: > 在 2016/6/23 8:29, Brian Norris 写道: > >On Thu, Jun 16, 2016 at 09:50:35AM +0800, Shawn Lin wrote: [...] > >>+ /* 500ms timeout value should be enough for gen1/2 taining */ > >>+ timeout = jiffies + msecs_to_jiffies(500); > >>+

<    1   2   3   4   5   6   7   8   9   10   >