From: Brian Norris <briannorris@chromium.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Benson Leung <bleung@chromium.org>,
chrome-platform@lists.linux.dev, linux-kernel@vger.kernel.org,
Samuel Holland <samuel@sholland.org>,
Julius Werner <jwerner@chromium.org>,
Stephen Boyd <swboyd@chromium.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] firmware: coreboot: Register bus in module init
Date: Fri, 21 Oct 2022 17:28:59 -0700 [thread overview]
Message-ID: <Y1M5Sw6Zs8PYzIIu@google.com> (raw)
In-Reply-To: <af9c4bfd-d3fb-1c7a-fb38-0d8bbd507449@roeck-us.net>
On Wed, Oct 19, 2022 at 06:20:08PM -0700, Guenter Roeck wrote:
> On 10/19/22 18:10, Brian Norris wrote:
> > Currently, get_maintainers.pl tells me Greg should pick this up. But I
> > CC the chrome-platform list too, since it seems reasonable for Google
> > folks (probably ChromeOS folks are most active here?) to maintain
> > Google/Chrome drivers.
> >
> > Let me know if y'all would like this official, and I'll push out a
> > MAINTAINERS patch.
> >
>
> I think that would be a good idea.
Done:
[PATCH] MAINTAINERS: Add drivers/firmware/google/ entry
https://lore.kernel.org/lkml/20221021172624.1.I119456791d197eb7d159f09e7479d8759008a954@changeid/
Brian
next prev parent reply other threads:[~2022-10-22 0:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 1:10 [PATCH] firmware: coreboot: Register bus in module init Brian Norris
2022-10-20 1:20 ` Guenter Roeck
2022-10-22 0:28 ` Brian Norris [this message]
2022-10-21 0:04 ` Stephen Boyd
2022-12-26 3:32 ` patchwork-bot+chrome-platform
2022-12-26 3:41 ` patchwork-bot+chrome-platform
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=Y1M5Sw6Zs8PYzIIu@google.com \
--to=briannorris@chromium.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=jwerner@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=samuel@sholland.org \
--cc=stable@vger.kernel.org \
--cc=swboyd@chromium.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