From: Joe Perches <joe@perches.com>
To: Jiri Kosina <jikos@kernel.org>, Jens Axboe <axboe@kernel.dk>
Cc: Kent Overstreet <kent.overstreet@gmail.com>,
Eric Wheeler <bcache@lists.ewheeler.net>,
linux-bcache@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] MAINTAINERS: mark bcache as orphan
Date: Tue, 24 May 2016 07:43:24 -0700 [thread overview]
Message-ID: <1464101004.1835.14.camel@perches.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1605241636520.31937@cbobk.fhfr.pm>
On Tue, 2016-05-24 at 16:38 +0200, Jiri Kosina wrote:
> The submitted patches are not being reacted upon, and Jens is only picking
> up stable fixes on an rather ad-hoc basis.
>
> Link: lkml.kernel.org/r/574462C5.40307@kernel.dk
> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 5f83015..c9906d6 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -2288,7 +2288,7 @@ BCACHE (BLOCK LAYER CACHE)
> M: Kent Overstreet <kent.overstreet@gmail.com>
> L: linux-bcache@vger.kernel.org
> W: http://bcache.evilpiepirate.org
> -S: Maintained
> +S: Orphan
> F: drivers/md/bcache/
Sections marked as Orphan generally
don't also have a named maintainer.
Should Kent still be listed here?
next prev parent reply other threads:[~2016-05-24 14:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 14:38 [PATCH 1/4] bcache: bch_writeback_thread() is not freezable Jiri Kosina
2016-05-24 14:38 ` [PATCH 2/4] bcache: bch_allocator_thread() " Jiri Kosina
2016-05-24 14:38 ` [PATCH 3/4] bcache: bch_gc_thread() " Jiri Kosina
2016-05-24 14:38 ` [PATCH 4/4] MAINTAINERS: mark bcache as orphan Jiri Kosina
2016-05-24 14:43 ` Joe Perches [this message]
2016-05-25 5:07 ` Jiri Kosina
2016-05-25 17:35 ` Jens Axboe
2016-05-24 15:01 ` [PATCH 1/4] bcache: bch_writeback_thread() is not freezable Jens Axboe
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=1464101004.1835.14.camel@perches.com \
--to=joe@perches.com \
--cc=axboe@kernel.dk \
--cc=bcache@lists.ewheeler.net \
--cc=jikos@kernel.org \
--cc=kent.overstreet@gmail.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).