From: Brian Norris <briannorris@chromium.org>
To: Tzung-Bi Shih <tzungbi@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Julius Werner <jwerner@chromium.org>,
chrome-platform@lists.linux.dev,
Guenter Roeck <linux@roeck-us.net>,
linux-kernel@vger.kernel.org, Stephen Boyd <swboyd@chromium.org>
Subject: Re: [PATCH] MAINTAINERS: Add drivers/firmware/google/ entry
Date: Mon, 24 Oct 2022 09:49:58 -0700 [thread overview]
Message-ID: <Y1bCNs76nTGWcS3l@google.com> (raw)
In-Reply-To: <Y1NlwY+RnKth++bW@google.com>
On Sat, Oct 22, 2022 at 11:38:41AM +0800, Tzung-Bi Shih wrote:
> On Fri, Oct 21, 2022 at 05:26:47PM -0700, Brian Norris wrote:
> > Per this conversation:
> > https://lore.kernel.org/lkml/af9c4bfd-d3fb-1c7a-fb38-0d8bbd507449@roeck-us.net/
> > Re: [PATCH] firmware: coreboot: Register bus in module init
> >
> > I guess if this is fine with folks, Tzung-Bi might queue this up?
>
> Ack, I can queue both if this is fine with folks.
I'll assume that might happen eventually.
> > +GOOGLE FIRMWARE DRIVERS
> > +M: Tzung-Bi Shih <tzungbi@google.com>
>
> Please use <tzungbi@kernel.org>. I prefer to use it for Linux community.
OK! I was just imitating your existing entry for CHROMEOS EC CODEC
DRIVER, which lists google.com email. So you might want to fix that one
if you want people mailing @kernel.org.
I'll assume you will fix that when applying. I can send a v2 if someone
else plans to commit it.
Brian
next prev parent reply other threads:[~2022-10-24 16:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-22 0:26 [PATCH] MAINTAINERS: Add drivers/firmware/google/ entry Brian Norris
2022-10-22 0:39 ` Julius Werner
2022-10-22 3:38 ` Tzung-Bi Shih
2022-10-24 16:49 ` Brian Norris [this message]
2022-10-25 1:40 ` Tzung-Bi Shih
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=Y1bCNs76nTGWcS3l@google.com \
--to=briannorris@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=swboyd@chromium.org \
--cc=tzungbi@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.