All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Tzung-Bi Shih <tzungbi@kernel.org>
To: bleung@chromium.org, groeck@chromium.org
Cc: gregkh@linuxfoundation.org, chrome-platform@lists.linux.dev,
	tzungbi@kernel.org, jwerner@chromium.org, swboyd@chromium.org,
	briannorris@chromium.org, dianders@chromium.org,
	sjg@chromium.org, dossym@chromium.org
Subject: [PATCH v2] MAINTAINERS: Add drivers/firmware/google/ entry
Date: Mon, 24 Jul 2023 16:12:47 +0800	[thread overview]
Message-ID: <20230724081247.678784-1-tzungbi@kernel.org> (raw)

From: Brian Norris <briannorris@chromium.org>

These are mostly used for Chrome platforms, so group it in with the same
mailing list, repo, and (one) committer.

Signed-off-by: Brian Norris <briannorris@chromium.org>
Acked-by: Julius Werner <jwerner@chromium.org>
Signed-off-by: Tzung-Bi Shih <tzungbi@kernel.org>
---
This is a revival for v1[1] as it is few-months-old.

Planning to let chrome-platform-firmware use:
- "for-firmware-kernelci" branch for KernelCI[2].
- "for-firmware-next" branch for both 0-day[3] and linux-next.  Patches can
  rebase onto the branch if they are aiming to chrome-platform-firmware.

Haven't figured out how to make it in linux-next specific files though
(e.g. [4]).

[1]: https://patchwork.kernel.org/project/chrome-platform/patch/20221021172624.1.I119456791d197eb7d159f09e7479d8759008a954@changeid/
[2]: https://github.com/kernelci/kernelci-core/pull/2028
[3]: https://github.com/intel/lkp-tests/pull/312
[4]: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=4d2c646ac07cf4a35ef1c4a935a1a4fd6c6b1a36

Changes from v1:
- Update Tzung-Bi's email address.

 MAINTAINERS | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index 3be1bdfe8ecc..8293a4ab82d8 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -8758,6 +8758,15 @@ S:	Supported
 F:	Documentation/networking/device_drivers/ethernet/google/gve.rst
 F:	drivers/net/ethernet/google
 
+GOOGLE FIRMWARE DRIVERS
+M:	Tzung-Bi Shih <tzungbi@kernel.org>
+R:	Brian Norris <briannorris@chromium.org>
+R:	Julius Werner <jwerner@chromium.org>
+L:	chrome-platform@lists.linux.dev
+S:	Maintained
+T:	git git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git
+F:	drivers/firmware/google/
+
 GPD POCKET FAN DRIVER
 M:	Hans de Goede <hdegoede@redhat.com>
 L:	platform-driver-x86@vger.kernel.org
-- 
2.41.0.487.g6d72f3e995-goog


             reply	other threads:[~2023-07-24  8:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-24  8:12 Tzung-Bi Shih [this message]
2023-07-24 13:42 ` [PATCH v2] MAINTAINERS: Add drivers/firmware/google/ entry Simon Glass
2023-07-24 14:24 ` Guenter Roeck
2023-07-24 16:12 ` Benson Leung
2023-09-11  4:31 ` patchwork-bot+chrome-platform
2023-09-11  4:49 ` 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=20230724081247.678784-1-tzungbi@kernel.org \
    --to=tzungbi@kernel.org \
    --cc=bleung@chromium.org \
    --cc=briannorris@chromium.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=dianders@chromium.org \
    --cc=dossym@chromium.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=groeck@chromium.org \
    --cc=jwerner@chromium.org \
    --cc=sjg@chromium.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 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.