Re: [PATCH v7 3/5] tpm: Clean up reading of timeout and duration capabilities

On Mon, Jun 20, 2016 at 06:54:00PM -0700, Ed Swierk wrote: > Call tpm_getcap() from tpm_get_timeouts() to eliminate redundant > code. Return all errors to the caller rather than swallowing them > (e.g. when tpm_transmit_cmd() returns nonzero). > > Signed-off-by: Ed Swierk

Re: [PATCH v7 3/5] tpm: Clean up reading of timeout and duration capabilities

On Mon, Jun 20, 2016 at 06:54:00PM -0700, Ed Swierk wrote: > Call tpm_getcap() from tpm_get_timeouts() to eliminate redundant > code. Return all errors to the caller rather than swallowing them > (e.g. when tpm_transmit_cmd() returns nonzero). > > Signed-off-by: Ed Swierk Reviewed-by: Jarkko

Re: [PATCH v2] pwm: improve args checking in pwm_apply_state()

On Tue, 21 Jun 2016 11:37:31 -0700 Brian Norris wrote: > Hi Geert, > > On Tue, Jun 21, 2016 at 04:42:04PM +0200, Geert Uytterhoeven wrote: > > On Fri, May 27, 2016 at 6:45 PM, Brian Norris > > wrote: > > > It seems like in the process of

Re: [PATCH v3 3/8] coccicheck: enable parmap support

On Tue, Jun 21, 2016 at 11:00:53PM +0200, Nicolas Palix (LIG) wrote: > Hi, > > Le 21/06/16 à 22:43, Julia Lawall a écrit : > > > > > >On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > > > >>On Tue, Jun 21, 2016 at 10:17:38PM +0200, Julia Lawall wrote: > >>> > >>> > >>>On Tue, 21 Jun 2016, Luis R.

Re: [PATCH v2] pwm: improve args checking in pwm_apply_state()

On Tue, 21 Jun 2016 11:37:31 -0700 Brian Norris wrote: > Hi Geert, > > On Tue, Jun 21, 2016 at 04:42:04PM +0200, Geert Uytterhoeven wrote: > > On Fri, May 27, 2016 at 6:45 PM, Brian Norris > > wrote: > > > It seems like in the process of refactoring pwm_config() to utilize the > > >

Re: [PATCH v3 3/8] coccicheck: enable parmap support

On Tue, Jun 21, 2016 at 11:00:53PM +0200, Nicolas Palix (LIG) wrote: > Hi, > > Le 21/06/16 à 22:43, Julia Lawall a écrit : > > > > > >On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > > > >>On Tue, Jun 21, 2016 at 10:17:38PM +0200, Julia Lawall wrote: > >>> > >>> > >>>On Tue, 21 Jun 2016, Luis R.

[PATCH v6 2/4] drm/i915/vlv: Reset the ADPA in vlv_display_power_well_init()

While VGA hotplugging worked(ish) before, it looks like that was mainly because we'd unintentionally enable it in valleyview_crt_detect_hotplug() when we did a force trigger. This doesn't work reliably enough because whenever the display powerwell on vlv gets disabled, the values set in VLV_ADPA

Re: [PATCH v3 3/8] coccicheck: enable parmap support

On Tue, Jun 21, 2016 at 11:10:00PM +0200, Julia Lawall wrote: > > > On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > > > On Tue, Jun 21, 2016 at 10:43:04PM +0200, Julia Lawall wrote: > > > > > > > > > On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > > > > > > > On Tue, Jun 21, 2016 at

Re: [PATCH v3 3/8] coccicheck: enable parmap support

On Tue, Jun 21, 2016 at 11:10:00PM +0200, Julia Lawall wrote: > > > On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > > > On Tue, Jun 21, 2016 at 10:43:04PM +0200, Julia Lawall wrote: > > > > > > > > > On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > > > > > > > On Tue, Jun 21, 2016 at

[PATCH v6 2/4] drm/i915/vlv: Reset the ADPA in vlv_display_power_well_init()

While VGA hotplugging worked(ish) before, it looks like that was mainly because we'd unintentionally enable it in valleyview_crt_detect_hotplug() when we did a force trigger. This doesn't work reliably enough because whenever the display powerwell on vlv gets disabled, the values set in VLV_ADPA

Re: [PATCH v2 01/17] RTC: ds1307: Add DS1341 variant

Please always include a commit message. On 21/06/2016 at 00:20:50 -0700, Andrey Smirnov wrote : > Signed-off-by: Andrey Smirnov > --- > drivers/rtc/rtc-ds1307.c | 5 + > 1 file changed, 5 insertions(+) > > diff --git a/drivers/rtc/rtc-ds1307.c

Re: [PATCH v2 01/17] RTC: ds1307: Add DS1341 variant

Please always include a commit message. On 21/06/2016 at 00:20:50 -0700, Andrey Smirnov wrote : > Signed-off-by: Andrey Smirnov > --- > drivers/rtc/rtc-ds1307.c | 5 + > 1 file changed, 5 insertions(+) > > diff --git a/drivers/rtc/rtc-ds1307.c b/drivers/rtc/rtc-ds1307.c > index

Re: [PATCH v3 3/8] coccicheck: enable parmap support

On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > On Tue, Jun 21, 2016 at 10:17:38PM +0200, Julia Lawall wrote: > > > > > > On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > > > > > Coccinelle has had parmap support since 1.0.2, this means > > > it supports --jobs, enabling built-in

Re: [PATCH v3 3/8] coccicheck: enable parmap support

On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > On Tue, Jun 21, 2016 at 10:17:38PM +0200, Julia Lawall wrote: > > > > > > On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > > > > > Coccinelle has had parmap support since 1.0.2, this means > > > it supports --jobs, enabling built-in

Re: [PATCH v3 5/8] scripts: add Linux .cocciconfig for coccinelle

On Tue, 21 Jun 2016, Nicolas Palix (LIG) wrote: > Le 21/06/16 à 21:21, Luis R. Rodriguez a écrit : > > Help Coccinelle when used against Linux with a set of sensible defaults > > options for Linux. This hints to coccinelle git can be used for 'git grep' > > queries over coccigrep. A timeout of

Re: [PATCH v3 5/8] scripts: add Linux .cocciconfig for coccinelle

On Tue, 21 Jun 2016, Nicolas Palix (LIG) wrote: > Le 21/06/16 à 21:21, Luis R. Rodriguez a écrit : > > Help Coccinelle when used against Linux with a set of sensible defaults > > options for Linux. This hints to coccinelle git can be used for 'git grep' > > queries over coccigrep. A timeout of

Re: [PATCH v2 13/17] RTC: ds1307: Report oscillator problems more intelligently

On 21/06/2016 at 00:22:46 -0700, Andrey Smirnov wrote : > Report oscillator problems more intelligently, by printing more > information about what cause the issue and not yelling "SET TIME!" at > the user. > Well, the proper way of doing that is to ensure that -EINVAL is returned when reading

Re: [PATCH v2 13/17] RTC: ds1307: Report oscillator problems more intelligently

On 21/06/2016 at 00:22:46 -0700, Andrey Smirnov wrote : > Report oscillator problems more intelligently, by printing more > information about what cause the issue and not yelling "SET TIME!" at > the user. > Well, the proper way of doing that is to ensure that -EINVAL is returned when reading

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

On Thu, Jun 16, 2016 at 12:06:03PM -0400, r...@redhat.com wrote: > +static unsigned long irqtime_account_hi_update(unsigned long max_jiffies) > { > u64 *cpustat = kcpustat_this_cpu->cpustat; > + unsigned long irq_jiffies; > unsigned long flags; > + u64 irq; > >

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

On Thu, Jun 16, 2016 at 12:06:03PM -0400, r...@redhat.com wrote: > +static unsigned long irqtime_account_hi_update(unsigned long max_jiffies) > { > u64 *cpustat = kcpustat_this_cpu->cpustat; > + unsigned long irq_jiffies; > unsigned long flags; > + u64 irq; > >

Re: [Cocci] [PATCH v3 0/8] coccicheck: modernize

On Tue, Jun 21, 2016 at 11:02:49PM +0200, Julia Lawall wrote: > On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > > That is sanitized as follows: > > > > # spatch only allows include directories with the syntax "-I include" > > > > # while gcc also allows "-Iinclude" and "-include

Re: [Cocci] [PATCH v3 0/8] coccicheck: modernize

On Tue, Jun 21, 2016 at 11:02:49PM +0200, Julia Lawall wrote: > On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > > That is sanitized as follows: > > > > # spatch only allows include directories with the syntax "-I include" > > > > # while gcc also allows "-Iinclude" and "-include

Re: Documenting ptrace access mode checking

On Tue, Jun 21, 2016 at 11:41:16AM +0200, Michael Kerrisk (man-pages) wrote: > Hi Jann, Stephen, et al. > > Jann, since you recently committed a patch in this area, and Stephen, > since you committed 006ebb40d3d much further back in time, I wonder if > you might help me by reviewing the text

Re: Documenting ptrace access mode checking

On Tue, Jun 21, 2016 at 11:41:16AM +0200, Michael Kerrisk (man-pages) wrote: > Hi Jann, Stephen, et al. > > Jann, since you recently committed a patch in this area, and Stephen, > since you committed 006ebb40d3d much further back in time, I wonder if > you might help me by reviewing the text

Re: [PATCH v2] scripts/gdb: add constants.py to .gitignore

On 21/06/16 22:11, Omar Sandoval wrote: > From: Omar Sandoval > > Since scripts/gdb/linux/constants.py is autogenerated, this should have > been added to .gitignore when it was introduced. > > Fixes: f197d75fcad1 ("scripts/gdb: provide linux constants") > Signed-off-by: Omar

Re: [PATCH v2] scripts/gdb: add constants.py to .gitignore

On 21/06/16 22:11, Omar Sandoval wrote: > From: Omar Sandoval > > Since scripts/gdb/linux/constants.py is autogenerated, this should have > been added to .gitignore when it was introduced. > > Fixes: f197d75fcad1 ("scripts/gdb: provide linux constants") > Signed-off-by: Omar Sandoval > --- >

Re: linux-next: Tree for Jun 21

On Tuesday, June 21, 2016 8:50:48 PM CEST Peter Zijlstra wrote: > > > So what's your build process for the cross tools, by the way? I'm assuming > > you're not doing a total bootstrap cross-tool build since you'd need minimal > > kernel headers (linux/errno.h or whatever) in that case. I assume

Re: linux-next: Tree for Jun 21

On Tuesday, June 21, 2016 8:50:48 PM CEST Peter Zijlstra wrote: > > > So what's your build process for the cross tools, by the way? I'm assuming > > you're not doing a total bootstrap cross-tool build since you'd need minimal > > kernel headers (linux/errno.h or whatever) in that case. I assume

[PATCH v2] scripts/gdb: add constants.py to .gitignore

From: Omar Sandoval Since scripts/gdb/linux/constants.py is autogenerated, this should have been added to .gitignore when it was introduced. Fixes: f197d75fcad1 ("scripts/gdb: provide linux constants") Signed-off-by: Omar Sandoval --- Thanks, Kieran, I totally

[PATCH v2] scripts/gdb: add constants.py to .gitignore

From: Omar Sandoval Since scripts/gdb/linux/constants.py is autogenerated, this should have been added to .gitignore when it was introduced. Fixes: f197d75fcad1 ("scripts/gdb: provide linux constants") Signed-off-by: Omar Sandoval --- Thanks, Kieran, I totally missed the comment in top-level

Re: [PATCH v3 7/8] coccicheck: refer to coccicheck bottest wiki for documentation

On Tue, 21 Jun 2016, Nicolas Palix (LIG) wrote: > Hi, > > Le 21/06/16 à 21:21, Luis R. Rodriguez a écrit : > > Sprinkling *tons* of documentation on the script is not a good > > idea, instead refer to a wiki for further coccicheck documentation: > > > >

Re: [PATCH v3 7/8] coccicheck: refer to coccicheck bottest wiki for documentation

On Tue, 21 Jun 2016, Nicolas Palix (LIG) wrote: > Hi, > > Le 21/06/16 à 21:21, Luis R. Rodriguez a écrit : > > Sprinkling *tons* of documentation on the script is not a good > > idea, instead refer to a wiki for further coccicheck documentation: > > > >

Re: [alsa-devel] [very-RFC 0/8] TSN driver for the kernel

On Tue, Jun 21, 2016 at 10:45:18AM -0700, Pierre-Louis Bossart wrote: > You can experiment with the 'dma' and 'link' timestamps today on any > HDaudio-based device. Like I said the synchronized part has not been > upstreamed yet (delays + dependency on ART-to-TSC conversions that made it > in the

Re: [alsa-devel] [very-RFC 0/8] TSN driver for the kernel

On Tue, Jun 21, 2016 at 10:45:18AM -0700, Pierre-Louis Bossart wrote: > You can experiment with the 'dma' and 'link' timestamps today on any > HDaudio-based device. Like I said the synchronized part has not been > upstreamed yet (delays + dependency on ART-to-TSC conversions that made it > in the

Re: [PATCH v2 02/17] RTC: ds1307: Disable square wave and timers as default

On 21/06/2016 at 00:22:35 -0700, Andrey Smirnov wrote : > Disable square wave and timers as default for DS1337/39/41 and > DS3231. The rationale being that configuring a chip this way puts it > into a known state with lower power consumption. While it is not very > likely it is still possible that

Re: [PATCH v2 02/17] RTC: ds1307: Disable square wave and timers as default

On 21/06/2016 at 00:22:35 -0700, Andrey Smirnov wrote : > Disable square wave and timers as default for DS1337/39/41 and > DS3231. The rationale being that configuring a chip this way puts it > into a known state with lower power consumption. While it is not very > likely it is still possible that

Re: [PATCH v3 7/8] coccicheck: refer to coccicheck bottest wiki for documentation

Hi, Le 21/06/16 à 21:21, Luis R. Rodriguez a écrit : Sprinkling *tons* of documentation on the script is not a good idea, instead refer to a wiki for further coccicheck documentation: https://bottest.wiki.kernel.org/coccicheck This page shall always refer to the linux-next iteration of

Re: [PATCH v3 7/8] coccicheck: refer to coccicheck bottest wiki for documentation

Hi, Le 21/06/16 à 21:21, Luis R. Rodriguez a écrit : Sprinkling *tons* of documentation on the script is not a good idea, instead refer to a wiki for further coccicheck documentation: https://bottest.wiki.kernel.org/coccicheck This page shall always refer to the linux-next iteration of

Re: [PATCH v8 3/8] perf tests: Add testcase for auxiliary evlist

Em Mon, Jun 20, 2016 at 10:47:20AM +, Wang Nan escreveu: > Improve test backward-ring-buffer, trace both enter and exit event of > prctl() syscall, utilize auxiliary evlist to mmap enter and exit event > into separated mmaps. > > Signed-off-by: Wang Nan > Cc: Arnaldo

Re: [PATCH v8 3/8] perf tests: Add testcase for auxiliary evlist

Em Mon, Jun 20, 2016 at 10:47:20AM +, Wang Nan escreveu: > Improve test backward-ring-buffer, trace both enter and exit event of > prctl() syscall, utilize auxiliary evlist to mmap enter and exit event > into separated mmaps. > > Signed-off-by: Wang Nan > Cc: Arnaldo Carvalho de Melo > Cc:

[PATCH v6 1/4] drm/i915/vlv: Make intel_crt_reset() per-encoder

This lets call intel_crt_reset() in contexts where IRQs are disabled and as such, can't hold the locks required to work with the connectors. Cc: sta...@vger.kernel.org Cc: Ville Syrjälä Acked-by: Daniel Vetter Signed-off-by: Lyude

[PATCH v6 4/4] drm/i915: Enable polling when we don't have hpd

Unfortunately, there's two situations where we lose hpd right now: - Runtime suspend - When we've shut off all of the power wells on Valleyview/Cherryview While it would be nice if this didn't cause issues, this has the ability to get us in some awkward states where a user won't be able to get

[PATCH v6 1/4] drm/i915/vlv: Make intel_crt_reset() per-encoder

This lets call intel_crt_reset() in contexts where IRQs are disabled and as such, can't hold the locks required to work with the connectors. Cc: sta...@vger.kernel.org Cc: Ville Syrjälä Acked-by: Daniel Vetter Signed-off-by: Lyude --- drivers/gpu/drm/i915/intel_crt.c | 10 +- 1 file

[PATCH v6 4/4] drm/i915: Enable polling when we don't have hpd

Unfortunately, there's two situations where we lose hpd right now: - Runtime suspend - When we've shut off all of the power wells on Valleyview/Cherryview While it would be nice if this didn't cause issues, this has the ability to get us in some awkward states where a user won't be able to get

[PATCH v5] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

If erasing or writing the BBT fails, we should mark the current BBT block as bad and use the BBT descriptor to scan for the next available unused block in the BBT. We should only return a failure if there isn't any space left. Based on original code implemented by Jeff Westfahl

[PATCH v6 0/4] Fixes for HPD

Latest version of: https://lists.freedesktop.org/archives/intel-gfx/2016-June/098787.html The only patch that's changed here is 4/4, the rest are just being sent so that they can be in one thread to make things easier for reviewers Lyude (4): drm/i915/vlv: Make intel_crt_reset() per-encoder

[PATCH v6 0/4] Fixes for HPD

Latest version of: https://lists.freedesktop.org/archives/intel-gfx/2016-June/098787.html The only patch that's changed here is 4/4, the rest are just being sent so that they can be in one thread to make things easier for reviewers Lyude (4): drm/i915/vlv: Make intel_crt_reset() per-encoder

[PATCH v5] mtd: nand_bbt: scan for next free bbt block if writing bbt fails

If erasing or writing the BBT fails, we should mark the current BBT block as bad and use the BBT descriptor to scan for the next available unused block in the BBT. We should only return a failure if there isn't any space left. Based on original code implemented by Jeff Westfahl . Signed-off-by:

[PATCH v6 3/4] drm/i915/vlv: Disable HPD in valleyview_crt_detect_hotplug()

One of the things preventing us from using polling is the fact that calling valleyview_crt_detect_hotplug() when there's a VGA cable connected results in sending another hotplug. With polling enabled when HPD is disabled, this results in a scenario like this: - We enable power wells and reset the

[PATCH v6 3/4] drm/i915/vlv: Disable HPD in valleyview_crt_detect_hotplug()

One of the things preventing us from using polling is the fact that calling valleyview_crt_detect_hotplug() when there's a VGA cable connected results in sending another hotplug. With polling enabled when HPD is disabled, this results in a scenario like this: - We enable power wells and reset the

Re: Documenting ptrace access mode checking

Kees Cook writes: > On Tue, Jun 21, 2016 at 12:55 PM, Eric W. Biederman > wrote: > >> "Michael Kerrisk (man-pages)" writes: >> >>>The algorithm employed for ptrace access mode checking deter‐ >>>mines

Re: Documenting ptrace access mode checking

Kees Cook writes: > On Tue, Jun 21, 2016 at 12:55 PM, Eric W. Biederman > wrote: > >> "Michael Kerrisk (man-pages)" writes: >> >>>The algorithm employed for ptrace access mode checking deter‐ >>>mines whether the calling process is allowed to perform the >>>

Re: [PATCH 3/3] staging: lowmemorykiller: select the task with maximum rss to kill

On Tue, 21 Jun 2016, Ganesh Mahendran wrote: > Current task selecting logic in LMK does not fully aware of the memory > pressure. It may select the task with maximum score adj, but with > least tasksize. > > For example, if min_score_adj is 200, and there are 2 tasks in system: >task a:

Re: [PATCH 3/3] staging: lowmemorykiller: select the task with maximum rss to kill

On Tue, 21 Jun 2016, Ganesh Mahendran wrote: > Current task selecting logic in LMK does not fully aware of the memory > pressure. It may select the task with maximum score adj, but with > least tasksize. > > For example, if min_score_adj is 200, and there are 2 tasks in system: >task a:

Re: [PATCH v3 3/8] coccicheck: enable parmap support

On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > On Tue, Jun 21, 2016 at 10:43:04PM +0200, Julia Lawall wrote: > > > > > > On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > > > > > On Tue, Jun 21, 2016 at 10:17:38PM +0200, Julia Lawall wrote: > > > > > > > > > > > > On Tue, 21 Jun 2016, Luis

Re: [PATCH v3 3/8] coccicheck: enable parmap support

On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > On Tue, Jun 21, 2016 at 10:43:04PM +0200, Julia Lawall wrote: > > > > > > On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > > > > > On Tue, Jun 21, 2016 at 10:17:38PM +0200, Julia Lawall wrote: > > > > > > > > > > > > On Tue, 21 Jun 2016, Luis

Re: [PATCH v3 5/8] scripts: add Linux .cocciconfig for coccinelle

Le 21/06/16 à 21:21, Luis R. Rodriguez a écrit : Help Coccinelle when used against Linux with a set of sensible defaults options for Linux. This hints to coccinelle git can be used for 'git grep' queries over coccigrep. A timeout of 200 seconds should suffice for now. If you use idutils you can

Re: [PATCH v3 5/8] scripts: add Linux .cocciconfig for coccinelle

Le 21/06/16 à 21:21, Luis R. Rodriguez a écrit : Help Coccinelle when used against Linux with a set of sensible defaults options for Linux. This hints to coccinelle git can be used for 'git grep' queries over coccigrep. A timeout of 200 seconds should suffice for now. If you use idutils you can

Re: [PATCH 03/13] RTC: ds1307: Add DS1341 specific power-saving options

On 21/06/2016 at 15:49:04 -0500, Rob Herring wrote : > So wouldn't you want to set one mode while running and the lower power > mode while suspended? I'm trying to understand the frequency of changing > this. If it is always one setting for a board, then yes it belongs in > DT. If it is a user

Re: [PATCH 03/13] RTC: ds1307: Add DS1341 specific power-saving options

On 21/06/2016 at 15:49:04 -0500, Rob Herring wrote : > So wouldn't you want to set one mode while running and the lower power > mode while suspended? I'm trying to understand the frequency of changing > this. If it is always one setting for a board, then yes it belongs in > DT. If it is a user

Re: [Cocci] [PATCH v3 0/8] coccicheck: modernize

On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > On Tue, Jun 21, 2016 at 10:13:31PM +0200, Julia Lawall wrote: > > > > > > On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > > > > > This v3 series addresses the feedback from the last v2 series > > > on the coccicheck enhancements [0], namely: > >

Re: [Intel-gfx] Bad flicker on skylake HQD due to code in the 4.7 merge window

On Tue, 2016-06-21 at 18:44 +0300, Ville Syrjälä wrote: > On Tue, Jun 21, 2016 at 09:53:15AM -0400, James Bottomley wrote: > > On Mon, 2016-06-20 at 11:03 +0300, Jani Nikula wrote: > > > Cc: Ville > > > > > > On Mon, 20 Jun 2016, James Bottomley < > > > james.bottom...@hansenpartnership.com>

Re: [Cocci] [PATCH v3 0/8] coccicheck: modernize

On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > On Tue, Jun 21, 2016 at 10:13:31PM +0200, Julia Lawall wrote: > > > > > > On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > > > > > This v3 series addresses the feedback from the last v2 series > > > on the coccicheck enhancements [0], namely: > >

Re: [Intel-gfx] Bad flicker on skylake HQD due to code in the 4.7 merge window

On Tue, 2016-06-21 at 18:44 +0300, Ville Syrjälä wrote: > On Tue, Jun 21, 2016 at 09:53:15AM -0400, James Bottomley wrote: > > On Mon, 2016-06-20 at 11:03 +0300, Jani Nikula wrote: > > > Cc: Ville > > > > > > On Mon, 20 Jun 2016, James Bottomley < > > > james.bottom...@hansenpartnership.com>

Re: [PATCH v3 3/8] coccicheck: enable parmap support

Hi, Le 21/06/16 à 22:43, Julia Lawall a écrit : On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: On Tue, Jun 21, 2016 at 10:17:38PM +0200, Julia Lawall wrote: On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: Coccinelle has had parmap support since 1.0.2, this means it supports --jobs,

Re: [PATCH v3 3/8] coccicheck: enable parmap support

Hi, Le 21/06/16 à 22:43, Julia Lawall a écrit : On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: On Tue, Jun 21, 2016 at 10:17:38PM +0200, Julia Lawall wrote: On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: Coccinelle has had parmap support since 1.0.2, this means it supports --jobs,

Re: [PATCH v7 5/5] tpm_tis: Increase ST19NP18 TPM command duration to avoid chip lockup

On Mon, Jun 20, 2016 at 06:54:02PM -0700, Ed Swierk wrote: > The STMicro ST19NP18-TPM sometimes takes much longer to execute > commands than it reports in its capabilities. For example, command 186 > (TPM_FlushSpecific) has been observed to take 14560 msec to complete, > far longer than the 3000

Re: [PATCH v7 5/5] tpm_tis: Increase ST19NP18 TPM command duration to avoid chip lockup

On Mon, Jun 20, 2016 at 06:54:02PM -0700, Ed Swierk wrote: > The STMicro ST19NP18-TPM sometimes takes much longer to execute > commands than it reports in its capabilities. For example, command 186 > (TPM_FlushSpecific) has been observed to take 14560 msec to complete, > far longer than the 3000

Re: [PATCH v3 3/8] coccicheck: enable parmap support

On Tue, Jun 21, 2016 at 10:43:04PM +0200, Julia Lawall wrote: > > > On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > > > On Tue, Jun 21, 2016 at 10:17:38PM +0200, Julia Lawall wrote: > > > > > > > > > On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > > > > > > > Coccinelle has had parmap

Re: [PATCH v3 3/8] coccicheck: enable parmap support

On Tue, Jun 21, 2016 at 10:43:04PM +0200, Julia Lawall wrote: > > > On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > > > On Tue, Jun 21, 2016 at 10:17:38PM +0200, Julia Lawall wrote: > > > > > > > > > On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > > > > > > > Coccinelle has had parmap

[PATCH v4 2/5] mmc: move 'parent' tracking to mmc_blk_data

In preparation for the removal of 'driverfs_dev' from 'struct gendisk', carry this data in mmc_blk_data. It is used for registration of parent disks and partitions. Cc: Ulf Hansson Reported-by: Bart Van Assche Signed-off-by: Dan Williams

[PATCH v4 2/5] mmc: move 'parent' tracking to mmc_blk_data

In preparation for the removal of 'driverfs_dev' from 'struct gendisk', carry this data in mmc_blk_data. It is used for registration of parent disks and partitions. Cc: Ulf Hansson Reported-by: Bart Van Assche Signed-off-by: Dan Williams --- drivers/mmc/card/block.c |5 +++-- 1 file

[PATCH v4 1/5] block: introduce device_add_disk()

In preparation for removing the ->driverfs_dev member of a gendisk, add an api that takes the parent device as a parameter to add_disk(). For now this maintains the status quo of WARN()ing on failure, but not return a error code. Reviewed-by: Christoph Hellwig Reviewed-by: Johannes

[PATCH v4 5/5] block: remove ->driverfs_dev

Now that all drivers that specify a ->driverfs_dev have been converted to device_add_disk(), the pointer can be removed from struct gendisk. Cc: Jens Axboe Cc: Ross Zwisler Reviewed-by: Christoph Hellwig Reviewed-by: Johannes Thumshirn

Re: [PATCH v7 4/5] tpm: Allow TPM chip drivers to override reported command durations

On Mon, Jun 20, 2016 at 06:54:01PM -0700, Ed Swierk wrote: > Some TPM chips report bogus command durations in their capabilities, > just as others report incorrect timeouts. Rework tpm_get_timeouts() to > allow chip drivers to override either via a single callback. Also > clean up handling of TPMs

[PATCH v4 1/5] block: introduce device_add_disk()

In preparation for removing the ->driverfs_dev member of a gendisk, add an api that takes the parent device as a parameter to add_disk(). For now this maintains the status quo of WARN()ing on failure, but not return a error code. Reviewed-by: Christoph Hellwig Reviewed-by: Johannes Thumshirn

[PATCH v4 5/5] block: remove ->driverfs_dev

Now that all drivers that specify a ->driverfs_dev have been converted to device_add_disk(), the pointer can be removed from struct gendisk. Cc: Jens Axboe Cc: Ross Zwisler Reviewed-by: Christoph Hellwig Reviewed-by: Johannes Thumshirn Signed-off-by: Dan Williams --- block/genhd.c |

Re: [PATCH v7 4/5] tpm: Allow TPM chip drivers to override reported command durations

On Mon, Jun 20, 2016 at 06:54:01PM -0700, Ed Swierk wrote: > Some TPM chips report bogus command durations in their capabilities, > just as others report incorrect timeouts. Rework tpm_get_timeouts() to > allow chip drivers to override either via a single callback. Also > clean up handling of TPMs

[PATCH v4 3/5] um: track 'parent' device in a local variable

In preparation for the removal of 'driverfs_dev' from 'struct gendisk' use a local variable to track the parented vs un-parented case in ubd_disk_register(). Cc: Jeff Dike Cc: Richard Weinberger Reported-by: Bart Van Assche

[PATCH v4 3/5] um: track 'parent' device in a local variable

In preparation for the removal of 'driverfs_dev' from 'struct gendisk' use a local variable to track the parented vs un-parented case in ubd_disk_register(). Cc: Jeff Dike Cc: Richard Weinberger Reported-by: Bart Van Assche Signed-off-by: Dan Williams --- arch/um/drivers/ubd_kern.c |5

Re: [Cocci] [PATCH v3 0/8] coccicheck: modernize

On Tue, Jun 21, 2016 at 10:13:31PM +0200, Julia Lawall wrote: > > > On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > > > This v3 series addresses the feedback from the last v2 series > > on the coccicheck enhancements [0], namely: > > > > o it drops the indexing heuristics in favor for a

Re: [Cocci] [PATCH v3 0/8] coccicheck: modernize

On Tue, Jun 21, 2016 at 10:13:31PM +0200, Julia Lawall wrote: > > > On Tue, 21 Jun 2016, Luis R. Rodriguez wrote: > > > This v3 series addresses the feedback from the last v2 series > > on the coccicheck enhancements [0], namely: > > > > o it drops the indexing heuristics in favor for a

Re: [RFC PATCHv2] usb: USB Type-C Connector Class

On Tue, 2016-06-21 at 16:58 +0300, Heikki Krogerus wrote: > On Tue, Jun 21, 2016 at 03:08:52PM +0200, Oliver Neukum wrote: > > > The firmware will surely want to display something. So it is possible > > that we start the OS will a valid power contract. How do we deal > > with that? Renegotiate?

Re: [RFC PATCHv2] usb: USB Type-C Connector Class

On Tue, 2016-06-21 at 16:58 +0300, Heikki Krogerus wrote: > On Tue, Jun 21, 2016 at 03:08:52PM +0200, Oliver Neukum wrote: > > > The firmware will surely want to display something. So it is possible > > that we start the OS will a valid power contract. How do we deal > > with that? Renegotiate?

[PATCH v4 4/5] block: convert to device_add_disk()

For block drivers that specify a parent device, convert them to use device_add_disk(). This conversion was done with the following semantic patch: @@ struct gendisk *disk; expression E; @@ - disk->driverfs_dev = E; ... - add_disk(disk); + device_add_disk(E,

[PATCH v4 4/5] block: convert to device_add_disk()

For block drivers that specify a parent device, convert them to use device_add_disk(). This conversion was done with the following semantic patch: @@ struct gendisk *disk; expression E; @@ - disk->driverfs_dev = E; ... - add_disk(disk); + device_add_disk(E,

[PATCH v4 0/5] Introduce device_add_disk() to kill gendisk.driverfs_dev

Changes since v3 [1]: 1/ Broke out the non-trivial conversions into their own patches. 2/ Fix a behavior change in arch/um/drivers/ubd_kern.c. This driver optionally creates parented and un-parented block devices. (Bart) 3/ Fix a behavior change in drivers/mmc/card/block.c. This driver does

[PATCH v4 0/5] Introduce device_add_disk() to kill gendisk.driverfs_dev

Changes since v3 [1]: 1/ Broke out the non-trivial conversions into their own patches. 2/ Fix a behavior change in arch/um/drivers/ubd_kern.c. This driver optionally creates parented and un-parented block devices. (Bart) 3/ Fix a behavior change in drivers/mmc/card/block.c. This driver does

Re: [patch] mm, compaction: abort free scanner if split fails

On Tue, 21 Jun 2016, Vlastimil Babka wrote: > > diff --git a/mm/compaction.c b/mm/compaction.c > > --- a/mm/compaction.c > > +++ b/mm/compaction.c > > @@ -494,24 +494,22 @@ static unsigned long isolate_freepages_block(struct > > compact_control *cc, > > > > /* Found a free page, will

Re: [patch] mm, compaction: abort free scanner if split fails

On Tue, 21 Jun 2016, Vlastimil Babka wrote: > > diff --git a/mm/compaction.c b/mm/compaction.c > > --- a/mm/compaction.c > > +++ b/mm/compaction.c > > @@ -494,24 +494,22 @@ static unsigned long isolate_freepages_block(struct > > compact_control *cc, > > > > /* Found a free page, will

Re: [PATCH 02/48] ARM: at91: Document new TCB bindings

On Wed, Jun 15, 2016 at 09:29:55AM +0200, Boris Brezillon wrote: > On Tue, 14 Jun 2016 16:47:37 -0500 > Rob Herring wrote: > > > On Sat, Jun 11, 2016 at 12:03:05AM +0200, Alexandre Belloni wrote: > > > The current binding for the TCB is not flexible enough for some use cases > >

Re: [PATCH 02/48] ARM: at91: Document new TCB bindings

On Wed, Jun 15, 2016 at 09:29:55AM +0200, Boris Brezillon wrote: > On Tue, 14 Jun 2016 16:47:37 -0500 > Rob Herring wrote: > > > On Sat, Jun 11, 2016 at 12:03:05AM +0200, Alexandre Belloni wrote: > > > The current binding for the TCB is not flexible enough for some use cases > > > and prevents

Re: Reported regressions for 4.7 as of Sunday, 2016-06-19

On Tue, Jun 21, 2016 at 4:11 AM, Josh Boyer wrote: > On Sun, Jun 19, 2016 at 10:52 AM, Thorsten Leemhuis > wrote: >> Description:BUG: unable to handle kernel NULL pointer dereference […] >> qla24xx_process_response_queue+0x49/0x4b0

Re: Reported regressions for 4.7 as of Sunday, 2016-06-19

On Tue, Jun 21, 2016 at 4:11 AM, Josh Boyer wrote: > On Sun, Jun 19, 2016 at 10:52 AM, Thorsten Leemhuis > wrote: >> Description:BUG: unable to handle kernel NULL pointer dereference […] >> qla24xx_process_response_queue+0x49/0x4b0 [qla2xxx] >> Report:

Re: [PATCH v4 0/1] pstore/ram: add Device Tree bindings

On Tue, Jun 14, 2016 at 09:40:47PM -0700, Kees Cook wrote: > On Tue, Jun 14, 2016 at 2:59 PM, Rob Herring wrote: > > On Fri, Jun 10, 2016 at 03:50:58PM -0700, Kees Cook wrote: > >> This is a "v4" of Greg Hackmann's DT bindings for ramoops. This is > >> what I'm going to land in

Re: [PATCH 1/2] workqueue: Move wq_update_unbound_numa() to the beginning of CPU_ONLINE

On Tue, Jun 21, 2016 at 11:36:51AM -0400, Tejun Heo wrote: > On Tue, Jun 21, 2016 at 07:42:31PM +0530, Gautham R Shenoy wrote: > > > Subject: [PATCH] sched: allow kthreads to fallback to online && !active > > > cpus > > > > > > During CPU hotplug, CPU_ONLINE callbacks are run while the CPU is >

[PATCH] coresight: delay initialisation when children are missing

Depending on when CoreSight device are discovered it is possible that some IP block may be referencing devices that have not been added to the bus yet. The end result is missing nodes in the CoreSight topology even when the devices are present and properly initialised. This patch solves the

Re: [PATCH v4 0/1] pstore/ram: add Device Tree bindings

On Tue, Jun 14, 2016 at 09:40:47PM -0700, Kees Cook wrote: > On Tue, Jun 14, 2016 at 2:59 PM, Rob Herring wrote: > > On Fri, Jun 10, 2016 at 03:50:58PM -0700, Kees Cook wrote: > >> This is a "v4" of Greg Hackmann's DT bindings for ramoops. This is > >> what I'm going to land in the pstore tree

Re: [PATCH 1/2] workqueue: Move wq_update_unbound_numa() to the beginning of CPU_ONLINE

On Tue, Jun 21, 2016 at 11:36:51AM -0400, Tejun Heo wrote: > On Tue, Jun 21, 2016 at 07:42:31PM +0530, Gautham R Shenoy wrote: > > > Subject: [PATCH] sched: allow kthreads to fallback to online && !active > > > cpus > > > > > > During CPU hotplug, CPU_ONLINE callbacks are run while the CPU is >

[PATCH] coresight: delay initialisation when children are missing

Depending on when CoreSight device are discovered it is possible that some IP block may be referencing devices that have not been added to the bus yet. The end result is missing nodes in the CoreSight topology even when the devices are present and properly initialised. This patch solves the

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