netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: gregkh@linuxfoundation.org
Cc: christian.brauner@ubuntu.com, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, rafael@kernel.org, pavel@ucw.cz,
	kuba@kernel.org, edumazet@google.com, stephen@networkplumber.org,
	linux-pm@vger.kernel.org
Subject: Re: [PATCH v6 0/9] net: fix sysfs permssions when device changes network
Date: Wed, 26 Feb 2020 17:37:50 -0800 (PST)	[thread overview]
Message-ID: <20200226.173750.2149877624295674225.davem@davemloft.net> (raw)
In-Reply-To: <20200226081757.GF24447@kroah.com>

From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date: Wed, 26 Feb 2020 09:17:57 +0100

> On Tue, Feb 25, 2020 at 02:19:29PM +0100, Christian Brauner wrote:
>> Hey everyone,
>> 
>> /* v6 */
>> This is v6 with two small fixups. I missed adapting the commit message
>> to reflect the renamed helper for changing the owner of sysfs files and
>> I also forgot to make the new dpm helper static inline.
> 
> All of the sysfs and driver core bits look good to me now.  Thanks for
> taking the time to update the documentation and other bits based on
> reviews.
> 
> So now it's just up to the netdev developers to review the netdev parts :)
> 
> The sysfs and driver core patches can all go through the netdev tree to
> make it easier for you.

I'm fine with these changes, and will apply this series to net-next.

Thanks everyone.

  reply	other threads:[~2020-02-27  1:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-25 13:19 [PATCH v6 0/9] net: fix sysfs permssions when device changes network Christian Brauner
2020-02-25 13:19 ` [PATCH v6 1/9] sysfs: add sysfs_file_change_owner() Christian Brauner
2020-02-26  8:13   ` Greg Kroah-Hartman
2020-02-25 13:19 ` [PATCH v6 2/9] sysfs: add sysfs_link_change_owner() Christian Brauner
2020-02-26  8:14   ` Greg Kroah-Hartman
2020-02-25 13:19 ` [PATCH v6 3/9] sysfs: add sysfs_group{s}_change_owner() Christian Brauner
2020-02-25 13:19 ` [PATCH v6 4/9] sysfs: add sysfs_change_owner() Christian Brauner
2020-02-26  8:15   ` Greg Kroah-Hartman
2020-02-25 13:19 ` [PATCH v6 5/9] device: add device_change_owner() Christian Brauner
2020-02-26  8:16   ` Greg Kroah-Hartman
2020-02-25 13:19 ` [PATCH v6 6/9] drivers/base/power: add dpm_sysfs_change_owner() Christian Brauner
2020-02-25 16:13   ` Rafael J. Wysocki
2020-02-26  8:16   ` Greg Kroah-Hartman
2020-02-25 13:19 ` [PATCH v6 7/9] net-sysfs: add netdev_change_owner() Christian Brauner
2020-02-25 13:19 ` [PATCH v6 8/9] net-sysfs: add queue_change_owner() Christian Brauner
2020-02-25 13:19 ` [PATCH v6 9/9] net: fix sysfs permssions when device changes network namespace Christian Brauner
2020-02-26  8:17 ` [PATCH v6 0/9] net: fix sysfs permssions when device changes network Greg Kroah-Hartman
2020-02-27  1:37   ` David Miller [this message]
2020-02-27  3:06     ` David Miller
2020-02-27  3:21       ` Christian Brauner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200226.173750.2149877624295674225.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=christian.brauner@ubuntu.com \
    --cc=edumazet@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rafael@kernel.org \
    --cc=stephen@networkplumber.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).