All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Benson Leung <bleung@google.com>
Cc: chrome-platform@lists.linux.dev,
	Benson Leung <bleung@chromium.org>,
	Rajat Jain <rajatja@google.com>
Subject: Re: [PATCH] MAINTAINERS: Add chrome-platform@lists.linux.dev to all Chrome OS entries
Date: Wed, 16 Mar 2022 15:00:44 -0700	[thread overview]
Message-ID: <dff75b5c-5ac2-843d-6a29-61f2eefc122a@roeck-us.net> (raw)
In-Reply-To: <YjJF71/B8Yb8cirZ@google.com>

On 3/16/22 13:17, Benson Leung wrote:
> Hi Guenter,
> 
> On Wed, Mar 16, 2022 at 11:49:45AM -0700, Guenter Roeck wrote:
>> Add the chrome-platform@lists.linux.dev mailing list to all Chrome OS
>> maintainer entries to ensure that people copy the list when submitting
>> Chrome OS specific patches. This also helps ensuring that patches are
>> available in a patchwork instance.
>>
>> Cc: Benson Leung <bleung@chromium.org>
>> Cc: Rajat Jain <rajatja@google.com>
>> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
> 
> I added this back in January.
> https://lore.kernel.org/r/20220126222233.2852280-1-bleung@chromium.org
> 
> It should already be in linux-next:
> https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git/commit/?h=for-next&id=664de6a26b7f17eebca896c3e18201b15d5c7b19
> 
> Let me know if it didn't show up there for you.
> 

Ah, I only checked mainline. Sorry for the noise.

Guenter

      reply	other threads:[~2022-03-16 22:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-16 18:49 [PATCH] MAINTAINERS: Add chrome-platform@lists.linux.dev to all Chrome OS entries Guenter Roeck
2022-03-16 20:17 ` Benson Leung
2022-03-16 22:00   ` Guenter Roeck [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=dff75b5c-5ac2-843d-6a29-61f2eefc122a@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=bleung@chromium.org \
    --cc=bleung@google.com \
    --cc=chrome-platform@lists.linux.dev \
    --cc=rajatja@google.com \
    /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.