All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: efremov@linux.com, 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, linux-block@vger.kernel.org,
	"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: floppy: take over maintainership
Date: Wed, 31 Jul 2019 08:53:22 -0600	[thread overview]
Message-ID: <431bd981-d81a-d4dd-75fe-96a29f8f1065@kernel.dk> (raw)
In-Reply-To: <57af5f3e-9cfe-b6d8-314c-f59855408cd5@linux.com>

On 7/31/19 8:47 AM, Denis Efremov wrote:
> 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

Great, can't see anyone objecting to doling out some floppy love.
Applied, thanks.

-- 
Jens Axboe


  reply	other threads:[~2019-07-31 14:53 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         ` [PATCH] MAINTAINERS: floppy: take over maintainership Denis Efremov
2019-07-31 14:53           ` Jens Axboe [this message]
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=431bd981-d81a-d4dd-75fe-96a29f8f1065@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=alex.popov@linux.com \
    --cc=efremov@ispras.ru \
    --cc=efremov@linux.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.