From: Joe Perches <joe@perches.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Stefani Seibold <stefani@seibold.net>,
Linus Walleij <linus.walleij@linaro.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: [RESEND PATCH] MAINTAINERS: add an entry for kfifo
Date: Mon, 13 Apr 2020 11:35:44 -0700 [thread overview]
Message-ID: <7e51e6c66c87bc6e466d688fa13ab75213706a06.camel@perches.com> (raw)
In-Reply-To: <20200413104250.26683-1-brgl@bgdev.pl>
On Mon, 2020-04-13 at 12:42 +0200, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
>
> Kfifo has been written by Stefani Seibold and she's implicitly expected to
> Ack any changes to it. She's not however officially listed as kfifo
> maintainer which leads to delays in patch review. This patch proposes to
> add an explicit entry for kfifo to MAINTAINERS file.
>
> Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> ---
> I'm not sure why this patch hasn't made it into v5.7 - it's been in next
> for weeks now. :(
>
> MAINTAINERS | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index e64e5db31497..f0f30b2cafa4 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -9412,6 +9412,13 @@ F: include/linux/keyctl.h
> F: include/uapi/linux/keyctl.h
> F: security/keys/
>
> +KFIFO
> +M: Stefani Seibold <stefani@seibold.net>
> +S: Maintained
> +F: lib/kfifo.c
> +F: include/linux/kfifo.h
> +F: samples/kfifo/
> +
trivia:
F: entries are now all sorted alphabetically.
Maybe switch the include and lib entries?
next prev parent reply other threads:[~2020-04-13 18:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 10:42 [RESEND PATCH] MAINTAINERS: add an entry for kfifo Bartosz Golaszewski
2020-04-13 10:49 ` Stefani Seibold
2020-04-13 18:35 ` Joe Perches [this message]
2020-04-13 20:09 ` Andrew Morton
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=7e51e6c66c87bc6e466d688fa13ab75213706a06.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bgolaszewski@baylibre.com \
--cc=brgl@bgdev.pl \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=stefani@seibold.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;
as well as URLs for NNTP newsgroup(s).