[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200729150100.GA3508555@kroah.com>
Date: Wed, 29 Jul 2020 17:01:00 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: "Rafael J. Wysocki" <rafael@...nel.org>
Cc: Abhishek Pandit-Subedi <abhishekpandit@...omium.org>,
Rafael Wysocki <rafael.j.wysocki@...el.com>,
Linux PM <linux-pm@...r.kernel.org>,
"open list:BLUETOOTH DRIVERS" <linux-bluetooth@...r.kernel.org>,
ChromeOS Bluetooth Upstreaming
<chromeos-bluetooth-upstreaming@...omium.org>,
Stephen Boyd <swboyd@...omium.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Len Brown <len.brown@...el.com>, Pavel Machek <pavel@....cz>
Subject: Re: [PATCH v5 1/1] power: Emit changed uevent on
wakeup_sysfs_add/remove
On Mon, Jul 27, 2020 at 03:38:02PM +0200, Rafael J. Wysocki wrote:
> On Thu, Jul 23, 2020 at 8:32 PM Greg Kroah-Hartman
> <gregkh@...uxfoundation.org> wrote:
> >
> > On Tue, Jul 07, 2020 at 10:28:44AM -0700, Abhishek Pandit-Subedi wrote:
> > > Udev rules that depend on the power/wakeup attribute don't get triggered
> > > correctly if device_set_wakeup_capable is called after the device is
> > > created. This can happen for several reasons (driver sets wakeup after
> > > device is created, wakeup is changed on parent device, etc) and it seems
> > > reasonable to emit a changed event when adding or removing attributes on
> > > the device.
> > >
> > > Signed-off-by: Abhishek Pandit-Subedi <abhishekpandit@...omium.org>
> >
> > Rafael, any objection to this? Do you want me to take it through my
> > tree, or are you going to take it through yours? Either is fine for me.
>
> It's already there in my tree with the R-by tag from you.
{sigh} Sorry for the noise.
greg k-h
Powered by blists - more mailing lists