From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Colin King <colin.king@canonical.com>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firmware: vpd: fix spelling mistake "partion" -> "partition"
Date: Thu, 13 Sep 2018 14:55:57 +0200 [thread overview]
Message-ID: <20180913125557.GA25003@kroah.com> (raw)
In-Reply-To: <20180912211011.GA20199@roeck-us.net>
On Wed, Sep 12, 2018 at 02:10:11PM -0700, Guenter Roeck wrote:
> On Wed, Sep 12, 2018 at 07:24:48AM +0200, Greg Kroah-Hartman wrote:
> > On Tue, Sep 11, 2018 at 09:58:48PM -0700, Guenter Roeck wrote:
> > > On 09/11/2018 09:58 AM, Colin King wrote:
> > > > From: Colin Ian King <colin.king@canonical.com>
> > > >
> > > > Trivial fix to spelling mistake in comment
> > > >
> > > > Signed-off-by: Colin Ian King <colin.king@canonical.com>
> > >
> > > Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> > >
> > > Interesting - drivers/firmware/google/ does not have a maintainer.
> > > Greg - is it correct to assume that you are the de-facto maintainer ?
> >
> > Yeah, I am :(
> >
>
> Hmm .. the :( doesn't sound too happy. Do you think we should have one ?
It's no fun when a driver ends up in the tree and no maintainer is
assigned to it, as that means I need to manage it myself. I've been
doing so since 2011, so it's not exactly a new experience, but as I have
no hardware for this, and honestly don't care at all about these
drivers, it's a very low priority for me to do anything with patches for
these files...
thanks,
greg k-h
prev parent reply other threads:[~2018-09-13 12:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 16:58 [PATCH] firmware: vpd: fix spelling mistake "partion" -> "partition" Colin King
2018-09-12 4:58 ` Guenter Roeck
2018-09-12 5:24 ` Greg Kroah-Hartman
2018-09-12 21:10 ` Guenter Roeck
2018-09-13 12:55 ` Greg Kroah-Hartman [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=20180913125557.GA25003@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=colin.king@canonical.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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