Re: rcu kernel-doc issues (4.14-rc1)

On Mon, Oct 16, 2017 at 02:46:15PM -0700, Randy Dunlap wrote: > On 10/16/17 13:26, Paul E. McKenney wrote: > > On Mon, Oct 16, 2017 at 01:18:14PM -0700, Randy Dunlap wrote: > >> On 10/16/17 13:07, Paul E. McKenney wrote: > >>> On Mon, Oct 16, 2017 at 12:58:28PM -0700, Randy Dunlap wrote: > Hi

[PATCH] documentation: kernel-api: add more info on bitmap functions

From: Randy Dunlap There are some good comments about bitmap operations in lib/bitmap.c and include/linux/bitmap.h, so format them for document generation and pull them into core-api/kernel-api.rst. I converted the "tables" of functions from using tabs to using spaces so

Re: [PATCH 01/12] PM / core: Add NEVER_SKIP and SMART_PREPARE driver flags

On Monday, October 16, 2017 8:31:22 AM CEST Greg Kroah-Hartman wrote: > On Mon, Oct 16, 2017 at 03:29:02AM +0200, Rafael J. Wysocki wrote: > > +static inline void dev_pm_set_driver_flags(struct device *dev, unsigned > > int flags) > > +{ > > + dev->power.driver_flags = flags; > > +} > > Should

Re: [PATCH 01/12] PM / core: Add NEVER_SKIP and SMART_PREPARE driver flags

On Monday, October 16, 2017 8:28:52 AM CEST Greg Kroah-Hartman wrote: > On Mon, Oct 16, 2017 at 03:29:02AM +0200, Rafael J. Wysocki wrote: > > struct dev_pm_info { > > pm_message_tpower_state; > > unsigned intcan_wakeup:1; > > @@ -561,6 +580,7 @@ struct dev_pm_info

Re: [PATCH 01/12] PM / core: Add NEVER_SKIP and SMART_PREPARE driver flags

On Monday, October 16, 2017 7:34:52 AM CEST Lukas Wunner wrote: > On Mon, Oct 16, 2017 at 03:29:02AM +0200, Rafael J. Wysocki wrote: > > + :c:func:`dev_pm_set_driver_flags` helper function.] If the first of > > + tese flags is set, the PM core will not apply the direct-complete > ^ >

Re: [PATCH 0/12] PM / sleep: Driver flags for system suspend/resume

On Mon, Oct 16, 2017 at 9:08 AM, Greg Kroah-Hartman wrote: > On Mon, Oct 16, 2017 at 03:12:35AM +0200, Rafael J. Wysocki wrote: >> Hi All, >> >> Well, this took more time than expected, as I tried to cover everything I had >> in mind regarding PM flags for drivers. >>

Re: rcu kernel-doc issues (4.14-rc1)

On 10/16/17 13:07, Paul E. McKenney wrote: > On Mon, Oct 16, 2017 at 12:58:28PM -0700, Randy Dunlap wrote: >> Hi Jonathan and Paul, >> >> Please include these fixes before 4.14 final. > > Hello, Randy, > > I currently have them queued up for the 4.15 merge window. Will that > work for you?

Re: [PATCH 01/12] PM / core: Add NEVER_SKIP and SMART_PREPARE driver flags

On Mon, 16 Oct 2017, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > The motivation for this change is to provide a way to work around > a problem with the direct-complete mechanism used for avoiding > system suspend/resume handling for devices in runtime

Re: rcu kernel-doc issues (4.14-rc1)

On Mon, Oct 16, 2017 at 12:58:28PM -0700, Randy Dunlap wrote: > Hi Jonathan and Paul, > > Please include these fixes before 4.14 final. Hello, Randy, I currently have them queued up for the 4.15 merge window. Will that work for you?

Re: rcu kernel-doc issues (4.14-rc1)

Hi Jonathan and Paul, Please include these fixes before 4.14 final. Thanks. On 09/17/17 12:49, Paul E. McKenney wrote: > On Sun, Sep 17, 2017 at 10:57:42AM -0700, Randy Dunlap wrote: >> On 09/17/17 10:47, Paul E. McKenney wrote: >>> On Sat, Sep 16, 2017 at 09:41:45PM -0700, Paul E. McKenney

Re: Documentation: add Kernel Driver Statement to the kernel

On Sat, 14 Oct 2017, "gre...@linuxfoundation.org" wrote: > And really, all news one should be in correct markdown format, as it is > almost identical to a "normal" text file. Heck, it really is just a > "plain" textfile, you can read it as-such, right? *cough*

Re: [PATCH 8/8] Documentation: fix ref to gpio.txt

On Thu, Oct 12, 2017 at 10:24 PM, Tom Saeger wrote: > Signed-off-by: Tom Saeger Patch applied. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majord...@vger.kernel.org More

[PATCH 2/2] mm: rename page dtor functions to {compound,huge,transhuge}_page__dtor

From: Changbin Du The current name free_{huge,transhuge}_page are paired with alloc_{huge,transhuge}_page functions, but the actual page free function is still free_page() which will indirectly call free_{huge,transhuge}_page. So this patch removes this confusion by

[PATCH 0/2] mm, thp: introduce dedicated transparent huge page allocation interfaces

From: Changbin Du The first one introduce new interfaces, the second one kills naming confusion. The aim is to remove duplicated code and simplify transparent huge page allocation. Changbin Du (2): mm, thp: introduce dedicated transparent huge page allocation

Re: [PATCH] PM / core: Fix kerneldoc comments of four functions

On 13 October 2017 at 15:25, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > Fix the kerneldoc comments of __device_suspend_noirq(), > __device_suspend_late() and __device_suspend() where the function > names in kerneldoc don't match the

Re: [PATCH 0/12] PM / sleep: Driver flags for system suspend/resume

On Mon, Oct 16, 2017 at 03:12:35AM +0200, Rafael J. Wysocki wrote: > Hi All, > > Well, this took more time than expected, as I tried to cover everything I had > in mind regarding PM flags for drivers. > > This work was triggered by attempts to fix and optimize PM in the > i2c-designware-platdev

Re: [PATCH 01/12] PM / core: Add NEVER_SKIP and SMART_PREPARE driver flags

On Mon, Oct 16, 2017 at 03:29:02AM +0200, Rafael J. Wysocki wrote: > +static inline void dev_pm_set_driver_flags(struct device *dev, unsigned int > flags) > +{ > + dev->power.driver_flags = flags; > +} Should this function just set the specific bit? Or is it going to be ok to set the whole

Re: [PATCH 01/12] PM / core: Add NEVER_SKIP and SMART_PREPARE driver flags

On Mon, Oct 16, 2017 at 03:29:02AM +0200, Rafael J. Wysocki wrote: > struct dev_pm_info { > pm_message_tpower_state; > unsigned intcan_wakeup:1; > @@ -561,6 +580,7 @@ struct dev_pm_info { > boolis_late_suspended:1; > bool