From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] driver core: bus.h: document bus notifiers better
Date: Wed, 18 Jan 2023 08:54:50 +0100 [thread overview]
Message-ID: <Y8elymzNMSHjDE/P@kroah.com> (raw)
In-Reply-To: <baf03556-718b-ea50-db48-04819a9cb094@infradead.org>
On Wed, Jan 11, 2023 at 11:29:12AM -0800, Randy Dunlap wrote:
>
>
> On 1/11/23 01:54, Rafael J. Wysocki wrote:
> > On Wed, Jan 11, 2023 at 10:23 AM Greg Kroah-Hartman
> > <gregkh@linuxfoundation.org> wrote:
> >>
> >> The bus notifier values are not documented all that well, so clean this
> >> up and make a real enumerated type for them and document them much
> >> better. When doing this, remove the hex values and just rely on the
> >> enumerated type instead as that is all that is needed.
> >>
> >> Cc: "Rafael J. Wysocki" <rafael@kernel.org>
> >> Cc: Randy Dunlap <rdunlap@infradead.org>
> >
> > I would add a Co-developed-by for Randy along with his sign-off (which
> > was given IIRC).
>
> or
> Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
> Either way; doesn't matter.
Thanks, I'll take it this way I don't have to respin it again :)
It's always the "simple" patches that take the most revisions...
greg k-h
prev parent reply other threads:[~2023-01-18 8:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 9:23 Greg Kroah-Hartman
2023-01-11 9:23 ` [PATCH v3 2/2] driver core: bus: move bus notifier logic into bus.c Greg Kroah-Hartman
2023-01-11 9:54 ` [PATCH v3 1/2] driver core: bus.h: document bus notifiers better Rafael J. Wysocki
2023-01-11 19:29 ` Randy Dunlap
2023-01-18 7:54 ` Greg Kroah-Hartman [this message]
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=Y8elymzNMSHjDE/P@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®