public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Guenter Roeck <groeck@google.com>,
	Stephen Boyd <swboyd@chromium.org>,
	Guenter Roeck <groeck@chromium.org>,
	Julius Werner <jwerner@chromium.org>,
	kernel-janitors@vger.kernel.org,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC] MAINTAINERS: include GOOGLE FIRMWARE entry
Date: Tue, 10 Mar 2020 07:48:40 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.21.2003100745590.2788@felia> (raw)
In-Reply-To: <69ed8a468b3e4776d277292a2e4b2f9b3c266f23.camel@perches.com>



On Mon, 9 Mar 2020, Joe Perches wrote:

> On Mon, 2020-03-09 at 22:03 +0100, Lukas Bulwahn wrote:
> > I am starting with the "bigger" clustered files in drivers, and then try 
> > > > to look at files in include and Documentation/ABI/.
> 
> If you want to spend the time tracking stuff down,
> it may be best to to
> start with include/
>

Thanks for the guidance. I will do that, and we will see if others 
appreciate that or not.


Lukas

      reply	other threads:[~2020-03-10  6:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-08 19:51 [PATCH RFC] MAINTAINERS: include GOOGLE FIRMWARE entry Lukas Bulwahn
2020-03-08 19:57 ` Greg Kroah-Hartman
2020-03-08 20:13 ` Joe Perches
2020-03-08 22:32 ` Guenter Roeck
2020-03-08 22:54   ` Joe Perches
2020-03-09  6:32     ` Lukas Bulwahn
2020-03-09  7:05       ` Greg Kroah-Hartman
2020-03-09 21:03         ` Lukas Bulwahn
2020-03-09 23:12           ` Joe Perches
2020-03-10  6:48             ` Lukas Bulwahn [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=alpine.DEB.2.21.2003100745590.2788@felia \
    --to=lukas.bulwahn@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=groeck@chromium.org \
    --cc=groeck@google.com \
    --cc=joe@perches.com \
    --cc=jwerner@chromium.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@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