From: Denis Efremov <efremov@linux.com>
To: Jiri Kosina <jikos@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Willy Tarreau <w@1wt.eu>, Will Deacon <will@kernel.org>,
Greg KH <greg@kroah.com>, Alexander Popov <alex.popov@linux.com>,
efremov@ispras.ru, Denis Efremov <efremov@linux.com>,
Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: [PATCH] MAINTAINERS: floppy: take over maintainership
Date: Wed, 31 Jul 2019 17:47:40 +0300 [thread overview]
Message-ID: <57af5f3e-9cfe-b6d8-314c-f59855408cd5@linux.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.1907172355020.5899@cbobk.fhfr.pm>
Hi All,
On 18.07.2019 01:03, Jiri Kosina wrote:
> On Wed, 17 Jul 2019, Linus Torvalds wrote:
>
>> I don't think we really have a floppy maintainer any more,
>
> Yeah, I basically volunteered myself to maintain it quite some time
> ago back when I fixed the concurrency issues which exhibited itself
> only with VM-emulated devices, and at the same time I still had the
> physical 3.5" reader.
>
> The hardware doesn't work any more though. So I guess I should just
> remove myself as a maintainer to reflect the reality and mark floppy.c
> as Orphaned.
Well, without jokes about Thunderdome, I've got time, hardware and
would like to maintain the floppy. Except the for recent fixes,
I described floppy ioctls in syzkaller. I've already spent quite
a lot of time with this code. Thus, if nobody minds
-- >8 --
From: Denis Efremov <efremov@linux.com>
Subject: [PATCH] MAINTAINERS: floppy: take over maintainership
I would like to maintain the floppy driver. After the recent fixes,
I think I know the code pretty well. Nowadays I've got 2 physical 3.5"
readers to test all the changes.
Signed-off-by: Denis Efremov <efremov@linux.com>
---
MAINTAINERS | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 6426db5198f0..6c49b48cfd69 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -6322,7 +6322,8 @@ F: Documentation/devicetree/bindings/counter/ftm-quaddec.txt
F: drivers/counter/ftm-quaddec.c
FLOPPY DRIVER
-S: Orphan
+M: Denis Efremov <efremov@linux.com>
+S: Odd Fixes
L: linux-block@vger.kernel.org
F: drivers/block/floppy.c
--
2.21.0
next parent reply other threads:[~2019-07-31 14:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190712185523.7208-1-efremov@ispras.ru>
[not found] ` <20190713080726.GA19611@1wt.eu>
[not found] ` <ec0a6c5e-bdee-3c26-f5d2-31b883c0de5d@ispras.ru>
[not found] ` <CAHk-=wi=fHuiQg1fMzqAP9cuykBQSN_feD=eALDwRPmw27UwEg@mail.gmail.com>
[not found] ` <nycvar.YFH.7.76.1907172355020.5899@cbobk.fhfr.pm>
2019-07-31 14:47 ` Denis Efremov [this message]
2019-07-31 14:53 ` [PATCH] MAINTAINERS: floppy: take over maintainership Jens Axboe
2019-07-31 15:22 ` Will Deacon
2019-07-31 15:31 ` Jens Axboe
2019-07-31 14:54 ` Willy Tarreau
2019-08-04 22:15 ` Jiri Kosina
2019-08-05 18:30 ` Thorsten Glaser
2019-08-08 7:43 ` Pavel Machek
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=57af5f3e-9cfe-b6d8-314c-f59855408cd5@linux.com \
--to=efremov@linux.com \
--cc=alex.popov@linux.com \
--cc=axboe@kernel.dk \
--cc=efremov@ispras.ru \
--cc=greg@kroah.com \
--cc=jikos@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=w@1wt.eu \
--cc=will@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).