Re: [PATCH v3 1/4] Ktest: add email support

On 04/06/2018 11:24 AM, Steven Rostedt wrote: On Mon, 26 Mar 2018 13:08:01 -0700 Tim Tianyang Chen wrote: Users can define optional variables to get email notifications. Ktest can send emails when the script: * was started * failed with fatal errors and called

Re: [PATCH v3 1/4] Ktest: add email support

On 04/06/2018 11:24 AM, Steven Rostedt wrote: On Mon, 26 Mar 2018 13:08:01 -0700 Tim Tianyang Chen wrote: Users can define optional variables to get email notifications. Ktest can send emails when the script: * was started * failed with fatal errors and called dodie() * completed all

Re: [PATCH 4.4 00/72] 4.4.127-stable review

On 04/06/2018 07:23 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.127 release. > There are 72 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

[PATCH v3 0/4] ktest: add email support

This patch set will let users define a mailer, an email address and when to receive notifications during automated testings. Users need to setup the specified mailer prior to using this feature. Tim Tianyang Chen (4): ktest: add email support ktest: add SigInt handling ktest: use dodie

[PATCH v3 0/4] ktest: add email support

This patch set will let users define a mailer, an email address and when to receive notifications during automated testings. Users need to setup the specified mailer prior to using this feature. Tim Tianyang Chen (4): ktest: add email support ktest: add SigInt handling ktest: use dodie

Re: [PATCH 4.4 00/72] 4.4.127-stable review

On 04/06/2018 07:23 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.127 release. > There are 72 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

[PATCH v3 2/4] ktest: add SigInt handling

User can cancel tests and specify handler's behavior using option 'EMAIL_WHEN_CANCELED'. Suggested-by: Dhaval Giani Signed-off-by: Tim Tianyang Chen --- tools/testing/ktest/ktest.pl | 10 ++ 1 file changed, 10 insertions(+) diff --git

[PATCH v3 2/4] ktest: add SigInt handling

User can cancel tests and specify handler's behavior using option 'EMAIL_WHEN_CANCELED'. Suggested-by: Dhaval Giani Signed-off-by: Tim Tianyang Chen --- tools/testing/ktest/ktest.pl | 10 ++ 1 file changed, 10 insertions(+) diff --git a/tools/testing/ktest/ktest.pl

[PATCH v3 1/4] ktest: add email support

Users can define optional variables to get email notifications. Ktest can send emails when the script: * was started * failed with fatal errors and called dodie() * completed all testing Users have to setup the mailer provided in config prior to using this script. Supported mailers: mailx,

[PATCH v3 1/4] ktest: add email support

Users can define optional variables to get email notifications. Ktest can send emails when the script: * was started * failed with fatal errors and called dodie() * completed all testing Users have to setup the mailer provided in config prior to using this script. Supported mailers: mailx,

[PATCH v3 4/4] ktest: add email options to sample.config

A block of email options is added under the optional config section. Suggested-by: Dhaval Giani Signed-off-by: Tim Tianyang Chen --- tools/testing/ktest/sample.conf | 22 ++ 1 file changed, 22 insertions(+) diff --git

[PATCH v3 3/4] ktest: use dodie for critical falures

Users should get emails when the script dies because of a critical failure. Critical failures are defined as any errors that could abnormally terminate the script. In order to add email support, this patch converts all die() to dodie() except: * when '-v' is used as an option to get the version

[PATCH v3 4/4] ktest: add email options to sample.config

A block of email options is added under the optional config section. Suggested-by: Dhaval Giani Signed-off-by: Tim Tianyang Chen --- tools/testing/ktest/sample.conf | 22 ++ 1 file changed, 22 insertions(+) diff --git a/tools/testing/ktest/sample.conf

[PATCH v3 3/4] ktest: use dodie for critical falures

Users should get emails when the script dies because of a critical failure. Critical failures are defined as any errors that could abnormally terminate the script. In order to add email support, this patch converts all die() to dodie() except: * when '-v' is used as an option to get the version

Re: [PATCH 4.9 000/102] 4.9.93-stable review

On 04/06/2018 07:22 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.93 release. > There are 102 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

Re: [PATCH 4.9 000/102] 4.9.93-stable review

On 04/06/2018 07:22 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.93 release. > There are 102 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

Re: [PATCH 4.14 00/67] 4.14.33-stable review

On 04/06/2018 07:23 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.33 release. > There are 67 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

Re: [PATCH 4.14 00/67] 4.14.33-stable review

On 04/06/2018 07:23 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.33 release. > There are 67 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

Re: [PATCH 0/8] livepatch: Atomic replace feature

On Fri, Mar 23, 2018 at 01:00:20PM +0100, Petr Mladek wrote: > The atomic replace allows to create cumulative patches. They > are useful when you maintain many livepatches and want to remove > one that is lower on the stack. In addition it is very useful when > more patches touch the same function

Re: [PATCH 0/8] livepatch: Atomic replace feature

On Fri, Mar 23, 2018 at 01:00:20PM +0100, Petr Mladek wrote: > The atomic replace allows to create cumulative patches. They > are useful when you maintain many livepatches and want to remove > one that is lower on the stack. In addition it is very useful when > more patches touch the same function

Re: [PATCH 4.15 00/72] 4.15.16-stable review

On 04/06/2018 07:23 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.15.16 release. > There are 72 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

Re: [PATCH 4.15 00/72] 4.15.16-stable review

On 04/06/2018 07:23 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.15.16 release. > There are 72 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

[PATCH] mmc: sdhci-pci: Only do AMD tuning for HS200

Commit c31165d7400b ("mmc: sdhci-pci: Add support for HS200 tuning mode on AMD, eMMC-4.5.1") added a HS200 tuning method for use with AMD SDHCI controllers. As described in the commit subject, this tuning is specific for HS200. However, as implemented, this method is used for all host timings,

[PATCH] mmc: sdhci-pci: Only do AMD tuning for HS200

Commit c31165d7400b ("mmc: sdhci-pci: Add support for HS200 tuning mode on AMD, eMMC-4.5.1") added a HS200 tuning method for use with AMD SDHCI controllers. As described in the commit subject, this tuning is specific for HS200. However, as implemented, this method is used for all host timings,

Re: [PATCH 4.16 00/31] 4.16.1-stable review

On 04/06/2018 07:24 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.16.1 release. > There are 31 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

Re: [PATCH 4.16 00/31] 4.16.1-stable review

On 04/06/2018 07:24 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.16.1 release. > There are 31 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

Re: [PATCH 6/8] livepatch: Remove Nop structures when unused

On Fri, Mar 23, 2018 at 01:00:26PM +0100, Petr Mladek wrote: > Replaced patches are removed from the stack when the transition is > finished. It means that Nop structures will never be needed again > and can be removed. Why should we care? Warning, grammar pedantry ahead. "Nop" isn't a proper

Re: [PATCH 6/8] livepatch: Remove Nop structures when unused

On Fri, Mar 23, 2018 at 01:00:26PM +0100, Petr Mladek wrote: > Replaced patches are removed from the stack when the transition is > finished. It means that Nop structures will never be needed again > and can be removed. Why should we care? Warning, grammar pedantry ahead. "Nop" isn't a proper

Re: [PATCH 4/8] livepatch: Add an extra flag to distinguish registered patches

On Fri, Mar 23, 2018 at 01:00:24PM +0100, Petr Mladek wrote: > @@ -528,6 +537,7 @@ static ssize_t enabled_store(struct kobject *kobj, struct > kobj_attribute *attr, > goto err; > } > > + > if (patch->enabled == enabled) { > /* already in requested state

Re: [PATCH 4/8] livepatch: Add an extra flag to distinguish registered patches

On Fri, Mar 23, 2018 at 01:00:24PM +0100, Petr Mladek wrote: > @@ -528,6 +537,7 @@ static ssize_t enabled_store(struct kobject *kobj, struct > kobj_attribute *attr, > goto err; > } > > + > if (patch->enabled == enabled) { > /* already in requested state

Re: [PATCH 3/8] livepatch: Add atomic replace

On Fri, Mar 23, 2018 at 01:00:23PM +0100, Petr Mladek wrote: > @@ -687,7 +858,14 @@ static void klp_free_patch(struct klp_patch *patch) > > static int klp_init_func(struct klp_object *obj, struct klp_func *func) > { > - if (!func->old_name || !func->new_func) > + if (!func->old_name) >

Re: [PATCH 3/8] livepatch: Add atomic replace

On Fri, Mar 23, 2018 at 01:00:23PM +0100, Petr Mladek wrote: > @@ -687,7 +858,14 @@ static void klp_free_patch(struct klp_patch *patch) > > static int klp_init_func(struct klp_object *obj, struct klp_func *func) > { > - if (!func->old_name || !func->new_func) > + if (!func->old_name) >

Re: call/normal switch was Re: omap4-droid4: voice call support was

On Fri 2018-04-06 14:23:46, Merlijn Wajer wrote: > Hi, > > On 06/04/18 14:04, Pavel Machek wrote: > > Hi! > > > >> OK that explains why the speaker keeps working then :) > > > > Ok, I pushed new version of unicsy_demo. > > > > It now sends & receives sms and you can call & receive call. Tone

Re: call/normal switch was Re: omap4-droid4: voice call support was

On Fri 2018-04-06 14:23:46, Merlijn Wajer wrote: > Hi, > > On 06/04/18 14:04, Pavel Machek wrote: > > Hi! > > > >> OK that explains why the speaker keeps working then :) > > > > Ok, I pushed new version of unicsy_demo. > > > > It now sends & receives sms and you can call & receive call. Tone

Re: AMD graphics performance regression in 4.15 and later

Hi Christian, Thanks for the info. FYI, I've also opened a Firefox bug for that at: https://bugzilla.mozilla.org/show_bug.cgi?id=1448778 Feel free to comment since you have a better understanding of what's going on. One last question: right now I'm running 4.15.0 with the "offending" patch

Re: AMD graphics performance regression in 4.15 and later

Hi Christian, Thanks for the info. FYI, I've also opened a Firefox bug for that at: https://bugzilla.mozilla.org/show_bug.cgi?id=1448778 Feel free to comment since you have a better understanding of what's going on. One last question: right now I'm running 4.15.0 with the "offending" patch

Re: [PATCH v4 1/3] locking: Document the semantics of spin_is_locked()

On Fri, Apr 06, 2018 at 02:08:16PM -0700, Randy Dunlap wrote: > On 04/06/2018 02:07 PM, Paul E. McKenney wrote: > > On Fri, Apr 06, 2018 at 02:01:41PM -0700, Randy Dunlap wrote: > >> On 04/06/2018 12:47 PM, Andrea Parri wrote: > >>> There appeared to be a certain, recurrent uncertainty concerning

Re: [PATCH v4 1/3] locking: Document the semantics of spin_is_locked()

On Fri, Apr 06, 2018 at 02:08:16PM -0700, Randy Dunlap wrote: > On 04/06/2018 02:07 PM, Paul E. McKenney wrote: > > On Fri, Apr 06, 2018 at 02:01:41PM -0700, Randy Dunlap wrote: > >> On 04/06/2018 12:47 PM, Andrea Parri wrote: > >>> There appeared to be a certain, recurrent uncertainty concerning

[tip:irq/core] genirq/affinity: Spread irq vectors among present CPUs as far as possible

Commit-ID: d3056812e7dfe6bf4f8ad9e397a9116dd5d32d15 Gitweb: https://git.kernel.org/tip/d3056812e7dfe6bf4f8ad9e397a9116dd5d32d15 Author: Ming Lei AuthorDate: Thu, 8 Mar 2018 18:53:58 +0800 Committer: Thomas Gleixner CommitDate: Fri, 6 Apr 2018

[tip:irq/core] genirq/affinity: Spread irq vectors among present CPUs as far as possible

Commit-ID: d3056812e7dfe6bf4f8ad9e397a9116dd5d32d15 Gitweb: https://git.kernel.org/tip/d3056812e7dfe6bf4f8ad9e397a9116dd5d32d15 Author: Ming Lei AuthorDate: Thu, 8 Mar 2018 18:53:58 +0800 Committer: Thomas Gleixner CommitDate: Fri, 6 Apr 2018 12:19:51 +0200 genirq/affinity: Spread irq

[tip:irq/core] genirq/affinity: Allow irq spreading from a given starting point

Commit-ID: 1a2d0914e23aab386f5d5acb689777e24151c2c8 Gitweb: https://git.kernel.org/tip/1a2d0914e23aab386f5d5acb689777e24151c2c8 Author: Ming Lei AuthorDate: Thu, 8 Mar 2018 18:53:57 +0800 Committer: Thomas Gleixner CommitDate: Fri, 6 Apr 2018

[tip:irq/core] genirq/affinity: Allow irq spreading from a given starting point

Commit-ID: 1a2d0914e23aab386f5d5acb689777e24151c2c8 Gitweb: https://git.kernel.org/tip/1a2d0914e23aab386f5d5acb689777e24151c2c8 Author: Ming Lei AuthorDate: Thu, 8 Mar 2018 18:53:57 +0800 Committer: Thomas Gleixner CommitDate: Fri, 6 Apr 2018 12:19:51 +0200 genirq/affinity: Allow irq

[tip:irq/core] genirq/affinity: Rename *node_to_possible_cpumask as *node_to_cpumask

Commit-ID: 47778f33dcba7feb92031643b37e477892f82b62 Gitweb: https://git.kernel.org/tip/47778f33dcba7feb92031643b37e477892f82b62 Author: Ming Lei AuthorDate: Thu, 8 Mar 2018 18:53:55 +0800 Committer: Thomas Gleixner CommitDate: Fri, 6 Apr 2018

[tip:irq/core] genirq/affinity: Rename *node_to_possible_cpumask as *node_to_cpumask

Commit-ID: 47778f33dcba7feb92031643b37e477892f82b62 Gitweb: https://git.kernel.org/tip/47778f33dcba7feb92031643b37e477892f82b62 Author: Ming Lei AuthorDate: Thu, 8 Mar 2018 18:53:55 +0800 Committer: Thomas Gleixner CommitDate: Fri, 6 Apr 2018 12:19:50 +0200 genirq/affinity: Rename

[tip:irq/core] genirq/affinity: Move actual irq vector spreading into a helper function

Commit-ID: b3e6aaa8d94d618e685c4df08bef991a4fb43923 Gitweb: https://git.kernel.org/tip/b3e6aaa8d94d618e685c4df08bef991a4fb43923 Author: Ming Lei AuthorDate: Thu, 8 Mar 2018 18:53:56 +0800 Committer: Thomas Gleixner CommitDate: Fri, 6 Apr 2018

[tip:irq/core] genirq/affinity: Move actual irq vector spreading into a helper function

Commit-ID: b3e6aaa8d94d618e685c4df08bef991a4fb43923 Gitweb: https://git.kernel.org/tip/b3e6aaa8d94d618e685c4df08bef991a4fb43923 Author: Ming Lei AuthorDate: Thu, 8 Mar 2018 18:53:56 +0800 Committer: Thomas Gleixner CommitDate: Fri, 6 Apr 2018 12:19:51 +0200 genirq/affinity: Move

Re: [PATCH V3 4/4] genirq/affinity: irq vector spread among online CPUs as far as possible

On Fri, 6 Apr 2018, Thomas Gleixner wrote: > On Fri, 6 Apr 2018, Ming Lei wrote: > > > > I will post V4 soon by using cpu_present_mask in the 1st stage irq spread. > > And it should work fine for Kashyap's case in normal cases. > > No need to resend. I've changed it already and will push it out

Re: [PATCH V3 4/4] genirq/affinity: irq vector spread among online CPUs as far as possible

On Fri, 6 Apr 2018, Thomas Gleixner wrote: > On Fri, 6 Apr 2018, Ming Lei wrote: > > > > I will post V4 soon by using cpu_present_mask in the 1st stage irq spread. > > And it should work fine for Kashyap's case in normal cases. > > No need to resend. I've changed it already and will push it out

Re: [PATCH ipmi/kcs_bmc v1] ipmi: kcs_bmc: optimize the data buffers allocation

On 03/15/2018 07:20 AM, Haiyue Wang wrote: Allocate a continuous memory block for the three KCS data buffers with related index assignment. I'm finally getting to this. Is there a reason you want to do this?  In general, it's better to not try to outsmart your base system.  Depending on the

Re: [PATCH ipmi/kcs_bmc v1] ipmi: kcs_bmc: optimize the data buffers allocation

On 03/15/2018 07:20 AM, Haiyue Wang wrote: Allocate a continuous memory block for the three KCS data buffers with related index assignment. I'm finally getting to this. Is there a reason you want to do this?  In general, it's better to not try to outsmart your base system.  Depending on the

Re: [PATCH] blk-cgroup: remove entries in blkg_tree before queue release

Hi Alexandru, Thank you for the patch! Yet something to improve: [auto build test ERROR on block/for-next] [also build test ERROR on v4.16 next-20180406] [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

Re: [PATCH] blk-cgroup: remove entries in blkg_tree before queue release

Hi Alexandru, Thank you for the patch! Yet something to improve: [auto build test ERROR on block/for-next] [also build test ERROR on v4.16 next-20180406] [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

Re: rcu_process_callbacks irqsoff latency caused by taking spinlock with irqs disabled

On Thu, 5 Apr 2018 08:53:20 -0700 "Paul E. McKenney" wrote: > On Thu, Apr 05, 2018 at 10:45:12AM +1000, Nicholas Piggin wrote: > > On Wed, 4 Apr 2018 17:13:58 -0700 > > "Paul E. McKenney" wrote: > > > > > On Thu, Apr 05, 2018 at

Re: rcu_process_callbacks irqsoff latency caused by taking spinlock with irqs disabled

On Thu, 5 Apr 2018 08:53:20 -0700 "Paul E. McKenney" wrote: > On Thu, Apr 05, 2018 at 10:45:12AM +1000, Nicholas Piggin wrote: > > On Wed, 4 Apr 2018 17:13:58 -0700 > > "Paul E. McKenney" wrote: > > > > > On Thu, Apr 05, 2018 at 09:34:14AM +1000, Nicholas Piggin wrote: > > > > Hi Paul, > >

[PATCH] mm/memblock: introduce PHYS_ADDR_MAX

So far code was using ULLONG_MAX and type casting to obtain a phys_addr_t with all bits set. The typecast is necessary to silence compiler warnings on 32-bit platforms. Use the simpler but still type safe approach "~(phys_addr_t)0" to create a preprocessor define for all bits set. Suggested-by:

[PATCH] mm/memblock: introduce PHYS_ADDR_MAX

So far code was using ULLONG_MAX and type casting to obtain a phys_addr_t with all bits set. The typecast is necessary to silence compiler warnings on 32-bit platforms. Use the simpler but still type safe approach "~(phys_addr_t)0" to create a preprocessor define for all bits set. Suggested-by:

Re: [PATCH v2] kbuild: check for pkg-config on make {menu,n,g,x}config

On 03/14/2018 10:50 PM, Masahiro Yamada wrote: > 2018-03-13 11:30 GMT+09:00 Randy Dunlap : >> From: Randy Dunlap >> >> Each of 'make {menu,n,g,x}config' uses (needs) pkg-config to make sure >> that other required files are present, but none of these

Re: [PATCH v2] kbuild: check for pkg-config on make {menu,n,g,x}config

On 03/14/2018 10:50 PM, Masahiro Yamada wrote: > 2018-03-13 11:30 GMT+09:00 Randy Dunlap : >> From: Randy Dunlap >> >> Each of 'make {menu,n,g,x}config' uses (needs) pkg-config to make sure >> that other required files are present, but none of these check that >> pkg-config itself is present.

Re: [PATCH v7 03/11] clk: actions: Add common clock driver support

Quoting Manivannan Sadhasivam (2018-03-26 10:38:57) > Add support for Actions Semi common clock driver with generic structures > and interface functions. > > Signed-off-by: Manivannan Sadhasivam > --- Applied to clk-next

Re: [PATCH v7 03/11] clk: actions: Add common clock driver support

Quoting Manivannan Sadhasivam (2018-03-26 10:38:57) > Add support for Actions Semi common clock driver with generic structures > and interface functions. > > Signed-off-by: Manivannan Sadhasivam > --- Applied to clk-next

Re: [PATCH v7 07/11] clk: actions: Add factor clock support

Quoting Manivannan Sadhasivam (2018-03-26 10:39:01) > Add support for Actions Semi factor clock together with > helper functions to be used in composite clock. > > Signed-off-by: Manivannan Sadhasivam > --- Applied to clk-next

Re: [PATCH v7 07/11] clk: actions: Add factor clock support

Quoting Manivannan Sadhasivam (2018-03-26 10:39:01) > Add support for Actions Semi factor clock together with > helper functions to be used in composite clock. > > Signed-off-by: Manivannan Sadhasivam > --- Applied to clk-next

Re: [PATCH v7 06/11] clk: actions: Add divider clock support

Quoting Manivannan Sadhasivam (2018-03-26 10:39:00) > Add support for Actions Semi divider clock together with > helper functions to be used in composite clock. > > Signed-off-by: Manivannan Sadhasivam > --- Applied to clk-next

Re: [PATCH v7 06/11] clk: actions: Add divider clock support

Quoting Manivannan Sadhasivam (2018-03-26 10:39:00) > Add support for Actions Semi divider clock together with > helper functions to be used in composite clock. > > Signed-off-by: Manivannan Sadhasivam > --- Applied to clk-next

Re: [PATCH v7 08/11] clk: actions: Add fixed factor clock support

Quoting Manivannan Sadhasivam (2018-03-26 10:39:02) > Add support for Actions Semi fixed factor clock reusing the clk > ops from common clock driver. > > Signed-off-by: Manivannan Sadhasivam > --- Applied to clk-next

Re: [PATCH v7 05/11] clk: actions: Add mux clock support

Quoting Manivannan Sadhasivam (2018-03-26 10:38:59) > Add support for Actions Semi mux clock together with helper > functions to be used in composite clock. > > Signed-off-by: Manivannan Sadhasivam > --- Applied to clk-next

Re: [PATCH v7 05/11] clk: actions: Add mux clock support

Quoting Manivannan Sadhasivam (2018-03-26 10:38:59) > Add support for Actions Semi mux clock together with helper > functions to be used in composite clock. > > Signed-off-by: Manivannan Sadhasivam > --- Applied to clk-next

Re: [PATCH v7 08/11] clk: actions: Add fixed factor clock support

Quoting Manivannan Sadhasivam (2018-03-26 10:39:02) > Add support for Actions Semi fixed factor clock reusing the clk > ops from common clock driver. > > Signed-off-by: Manivannan Sadhasivam > --- Applied to clk-next

Re: [PATCH v7 04/11] clk: actions: Add gate clock support

Quoting Manivannan Sadhasivam (2018-03-26 10:38:58) > Add support for Actions Semi gate clock together with helper > functions to be used in composite clock. > > Signed-off-by: Manivannan Sadhasivam > --- Applied to clk-next

Re: [PATCH v7 10/11] clk: actions: Add pll clock support

Quoting Manivannan Sadhasivam (2018-03-26 10:39:04) > Add support for Actions Semi PLL clock. > > Signed-off-by: Manivannan Sadhasivam > --- Applied to clk-next

Re: [PATCH v7 04/11] clk: actions: Add gate clock support

Quoting Manivannan Sadhasivam (2018-03-26 10:38:58) > Add support for Actions Semi gate clock together with helper > functions to be used in composite clock. > > Signed-off-by: Manivannan Sadhasivam > --- Applied to clk-next

Re: [PATCH v7 10/11] clk: actions: Add pll clock support

Quoting Manivannan Sadhasivam (2018-03-26 10:39:04) > Add support for Actions Semi PLL clock. > > Signed-off-by: Manivannan Sadhasivam > --- Applied to clk-next

Re: [PATCH v7 09/11] clk: actions: Add composite clock support

Quoting Manivannan Sadhasivam (2018-03-26 10:39:03) > Add support for Actions Semi composite clock. This clock > consists of gate, mux, divider, factor and fixed factor clocks. > > Signed-off-by: Manivannan Sadhasivam > --- Applied to clk-next

Re: [PATCH v7 09/11] clk: actions: Add composite clock support

Quoting Manivannan Sadhasivam (2018-03-26 10:39:03) > Add support for Actions Semi composite clock. This clock > consists of gate, mux, divider, factor and fixed factor clocks. > > Signed-off-by: Manivannan Sadhasivam > --- Applied to clk-next

Re: [PATCH v7 11/11] clk: actions: Add S900 SoC clock support

Quoting Manivannan Sadhasivam (2018-03-26 10:39:05) > Add Actions Semi S900 SoC clock support. > > Signed-off-by: Manivannan Sadhasivam > --- Applied to clk-next

Re: [PATCH v7 11/11] clk: actions: Add S900 SoC clock support

Quoting Manivannan Sadhasivam (2018-03-26 10:39:05) > Add Actions Semi S900 SoC clock support. > > Signed-off-by: Manivannan Sadhasivam > --- Applied to clk-next

[GIT PULL] VFIO updates for v4.17

Hi Linus, The following changes since commit c698ca5278934c0ae32297a8725ced2e27585d7f: Linux 4.16-rc6 (2018-03-18 17:48:42 -0700) are available in the Git repository at: git://github.com/awilliam/linux-vfio.git tags/vfio-v4.17-rc1 for you to fetch changes up to

[GIT PULL] VFIO updates for v4.17

Hi Linus, The following changes since commit c698ca5278934c0ae32297a8725ced2e27585d7f: Linux 4.16-rc6 (2018-03-18 17:48:42 -0700) are available in the Git repository at: git://github.com/awilliam/linux-vfio.git tags/vfio-v4.17-rc1 for you to fetch changes up to

Re: [Patch 0/4] RFC : Support for data gradation of a single file.

On Apr 6, 2018, at 5:41 AM, Sayan Ghosh wrote: > > Hi all, > > The following series of patches aim to store a file with a graded > information. Consider a scenario of video indexing for learning > programme where some of the portions of the video is annotated and >

Re: [Patch 0/4] RFC : Support for data gradation of a single file.

On Apr 6, 2018, at 5:41 AM, Sayan Ghosh wrote: > > Hi all, > > The following series of patches aim to store a file with a graded > information. Consider a scenario of video indexing for learning > programme where some of the portions of the video is annotated and > important than other

Re: atomic file replacing status?

On Fri, Apr 06, 2018 at 02:22:06PM -0700, Randy Dunlap wrote: > On 02/11/2018 10:40 PM, Andrew Kelley wrote: > > Whatever happened to this patch? > > > > https://patchwork.kernel.org/patch/9636735/ > > > > It looks fine and addresses a legitimate issue. > > > > Please CC me on replies as I am

Re: atomic file replacing status?

On Fri, Apr 06, 2018 at 02:22:06PM -0700, Randy Dunlap wrote: > On 02/11/2018 10:40 PM, Andrew Kelley wrote: > > Whatever happened to this patch? > > > > https://patchwork.kernel.org/patch/9636735/ > > > > It looks fine and addresses a legitimate issue. > > > > Please CC me on replies as I am

Re: [PATCH v3 2/2] MIPS: io: add a barrier after register read in readX()

On Fri, Apr 06, 2018 at 02:15:57PM -0400, Sinan Kaya wrote: > On 4/5/2018 9:34 PM, Sinan Kaya wrote: > > Can we get these merged to 4.17? > > > > There was a consensus to fix the architectures having API violation issues. > > https://www.mail-archive.com/netdev@vger.kernel.org/msg225971.html > >

Re: [PATCH v3 2/2] MIPS: io: add a barrier after register read in readX()

On Fri, Apr 06, 2018 at 02:15:57PM -0400, Sinan Kaya wrote: > On 4/5/2018 9:34 PM, Sinan Kaya wrote: > > Can we get these merged to 4.17? > > > > There was a consensus to fix the architectures having API violation issues. > > https://www.mail-archive.com/netdev@vger.kernel.org/msg225971.html > >

Re: atomic file replacing status?

On 02/11/2018 10:40 PM, Andrew Kelley wrote: > Whatever happened to this patch? > > https://patchwork.kernel.org/patch/9636735/ > > It looks fine and addresses a legitimate issue. > > Please CC me on replies as I am not subscribed to the LKML. > > Kind regards, > Andrew Kelley There was some

Re: atomic file replacing status?

On 02/11/2018 10:40 PM, Andrew Kelley wrote: > Whatever happened to this patch? > > https://patchwork.kernel.org/patch/9636735/ > > It looks fine and addresses a legitimate issue. > > Please CC me on replies as I am not subscribed to the LKML. > > Kind regards, > Andrew Kelley There was some

Re: INFO: rcu detected stall in snd_pcm_oss_write3 (2)

syzbot has found reproducer for the following crash on upstream commit 38c23685b273cfb4ccf31a199feccce3bdcb5d83 (Fri Apr 6 04:29:35 2018 +) Merge tag 'armsoc-drivers' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc syzbot dashboard link:

Re: INFO: rcu detected stall in snd_pcm_oss_write3 (2)

syzbot has found reproducer for the following crash on upstream commit 38c23685b273cfb4ccf31a199feccce3bdcb5d83 (Fri Apr 6 04:29:35 2018 +) Merge tag 'armsoc-drivers' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc syzbot dashboard link:

Re: [PATCH 02/10] locking/qspinlock: Remove unbounded cmpxchg loop from locking slowpath

On Fri, Apr 06, 2018 at 04:50:19PM -0400, Waiman Long wrote: > On 04/05/2018 12:58 PM, Will Deacon wrote: > > The qspinlock locking slowpath utilises a "pending" bit as a simple form > > of an embedded test-and-set lock that can avoid the overhead of explicit > > queuing in cases where the lock is

Re: [PATCH 02/10] locking/qspinlock: Remove unbounded cmpxchg loop from locking slowpath

On Fri, Apr 06, 2018 at 04:50:19PM -0400, Waiman Long wrote: > On 04/05/2018 12:58 PM, Will Deacon wrote: > > The qspinlock locking slowpath utilises a "pending" bit as a simple form > > of an embedded test-and-set lock that can avoid the overhead of explicit > > queuing in cases where the lock is

Re: [PATCH v4 1/3] locking: Document the semantics of spin_is_locked()

On 04/06/2018 02:07 PM, Paul E. McKenney wrote: > On Fri, Apr 06, 2018 at 02:01:41PM -0700, Randy Dunlap wrote: >> On 04/06/2018 12:47 PM, Andrea Parri wrote: >>> There appeared to be a certain, recurrent uncertainty concerning the >>> semantics of spin_is_locked(), likely a consequence of the

Re: [PATCH v4 1/3] locking: Document the semantics of spin_is_locked()

On 04/06/2018 02:07 PM, Paul E. McKenney wrote: > On Fri, Apr 06, 2018 at 02:01:41PM -0700, Randy Dunlap wrote: >> On 04/06/2018 12:47 PM, Andrea Parri wrote: >>> There appeared to be a certain, recurrent uncertainty concerning the >>> semantics of spin_is_locked(), likely a consequence of the

Re: [PATCH v4 1/3] locking: Document the semantics of spin_is_locked()

On Fri, Apr 06, 2018 at 02:01:41PM -0700, Randy Dunlap wrote: > On 04/06/2018 12:47 PM, Andrea Parri wrote: > > There appeared to be a certain, recurrent uncertainty concerning the > > semantics of spin_is_locked(), likely a consequence of the fact that > > this semantics remains undocumented or

Re: [PATCH v4 1/3] locking: Document the semantics of spin_is_locked()

On Fri, Apr 06, 2018 at 02:01:41PM -0700, Randy Dunlap wrote: > On 04/06/2018 12:47 PM, Andrea Parri wrote: > > There appeared to be a certain, recurrent uncertainty concerning the > > semantics of spin_is_locked(), likely a consequence of the fact that > > this semantics remains undocumented or

[GIT PULL] kselftest update for 4.17-rc1

Hi Linus, Please pull the following Kselftest update for 4.17-rc1 This Kselftest update for 4.17-rc1 consists of: - Test build error fixes. - Fixes to prevent intel_pstate from building on non-x86 systems. - New test for ion with vgem driver. - Change to print the test name to /dev/kmsg to add

[GIT PULL] kselftest update for 4.17-rc1

Hi Linus, Please pull the following Kselftest update for 4.17-rc1 This Kselftest update for 4.17-rc1 consists of: - Test build error fixes. - Fixes to prevent intel_pstate from building on non-x86 systems. - New test for ion with vgem driver. - Change to print the test name to /dev/kmsg to add

[PATCH] staging: pi433: break long lines in rf69.c

Breaks long lines in rf69.c, fixing checkpatch.pl warnings: "WARNING: line over 80 characters" Signed-off-by: Simon Sandström --- drivers/staging/pi433/rf69.c | 182 ++- 1 file changed, 129 insertions(+), 53 deletions(-) diff --git

[PATCH] staging: pi433: break long lines in rf69.c

Breaks long lines in rf69.c, fixing checkpatch.pl warnings: "WARNING: line over 80 characters" Signed-off-by: Simon Sandström --- drivers/staging/pi433/rf69.c | 182 ++- 1 file changed, 129 insertions(+), 53 deletions(-) diff --git

Re: [PATCH v2] isofs compress: Remove VLA usage

On Thu, 2018-04-05 at 11:17 -0700, Kyle Spiers wrote: > As part of the effort to remove VLAs from the kernel[1], this changes > the allocation of the bhs and pages arrays from being on the stack to being > kcalloc()ed. This also allows for the removal of the explicit zeroing > of bhs. > >

Re: [PATCH v2] isofs compress: Remove VLA usage

On Thu, 2018-04-05 at 11:17 -0700, Kyle Spiers wrote: > As part of the effort to remove VLAs from the kernel[1], this changes > the allocation of the bhs and pages arrays from being on the stack to being > kcalloc()ed. This also allows for the removal of the explicit zeroing > of bhs. > >

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