lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFztTY8gGh=eLD65QuaUA8dpKxXqJbQimV+7PnbWqMDyzw@mail.gmail.com>
Date:	Tue, 11 Jun 2013 20:09:24 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Matthew Wilcox <willy@...ux.intel.com>
Cc:	linux-nvme@...ts.infradead.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PULL REQUEST] NVMe driver fixes

On Tue, Jun 11, 2013 at 2:04 PM, Matthew Wilcox <willy@...ux.intel.com> wrote:
>
> The following bugfixes have been accumulating for the last few weeks, and
> it would be nice if they could be in 3.10.

So I'm not in the least sure I should bother with the whole nvme thing.

It's after -rc5, and this pattern of "stuff comes in quite late in the
merge window, and then even later in the rc series" is getting really
tiresome.

I'm getting a strong signal of "this driver isn't something people
bother to actually maintain". Do you even have access to hardware by
now? I've gotten all of four pull requests for this driver if I look
at the logs correctly, and of those four pull requests one was after
an rc7, and now this is after an rc5.

Simple question: is it worth the bother?

                 Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ