From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Keith Busch <keith.busch@intel.com>,
linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Subject: Re: [GIT PULL] nvme fixes for 4.20
Date: Fri, 30 Nov 2018 10:12:06 -0700 [thread overview]
Message-ID: <08296696-8fd5-1c99-1df2-39ccda11dea7@kernel.dk> (raw)
In-Reply-To: <20181130162633.GA16933@infradead.org>
On 11/30/18 9:26 AM, Christoph Hellwig wrote:
> On Fri, Nov 30, 2018 at 08:26:24AM -0700, Jens Axboe wrote:
>> On 11/30/18 8:24 AM, Christoph Hellwig wrote:
>>> Various fixlets all over, including throwing in a 'default y' for the
>>> multipath code, given that we want people to actually enable it for full
>>> functionality.
>>
>> Why enable it by default? 99.9% of users aren't going to care. That
>> seems like an odd choice.
>
> Because its small, and if you don't have it you are going to run into
> problems pretty soon.
Let's do it for 4.21...
> Anyway, to get the fixes out ASAP here is the updated request without
> it:
Pulled, thanks.
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: axboe@kernel.dk (Jens Axboe)
Subject: [GIT PULL] nvme fixes for 4.20
Date: Fri, 30 Nov 2018 10:12:06 -0700 [thread overview]
Message-ID: <08296696-8fd5-1c99-1df2-39ccda11dea7@kernel.dk> (raw)
In-Reply-To: <20181130162633.GA16933@infradead.org>
On 11/30/18 9:26 AM, Christoph Hellwig wrote:
> On Fri, Nov 30, 2018@08:26:24AM -0700, Jens Axboe wrote:
>> On 11/30/18 8:24 AM, Christoph Hellwig wrote:
>>> Various fixlets all over, including throwing in a 'default y' for the
>>> multipath code, given that we want people to actually enable it for full
>>> functionality.
>>
>> Why enable it by default? 99.9% of users aren't going to care. That
>> seems like an odd choice.
>
> Because its small, and if you don't have it you are going to run into
> problems pretty soon.
Let's do it for 4.21...
> Anyway, to get the fixes out ASAP here is the updated request without
> it:
Pulled, thanks.
--
Jens Axboe
next prev parent reply other threads:[~2018-11-30 17:12 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 15:24 [GIT PULL] nvme fixes for 4.20 Christoph Hellwig
2018-11-30 15:24 ` Christoph Hellwig
2018-11-30 15:26 ` Jens Axboe
2018-11-30 15:26 ` Jens Axboe
2018-11-30 15:37 ` Keith Busch
2018-11-30 15:37 ` Keith Busch
2018-11-30 16:26 ` Christoph Hellwig
2018-11-30 16:26 ` Christoph Hellwig
2018-11-30 17:12 ` Jens Axboe [this message]
2018-11-30 17:12 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2018-12-07 15:38 Christoph Hellwig
2018-12-07 15:38 ` Christoph Hellwig
2018-12-07 15:40 ` Jens Axboe
2018-12-07 15:40 ` Jens Axboe
2018-11-09 6:56 Christoph Hellwig
2018-11-09 6:56 ` Christoph Hellwig
2018-11-09 13:16 ` Jens Axboe
2018-11-09 13:16 ` Jens Axboe
2018-11-09 13:20 ` Christoph Hellwig
2018-11-09 13:20 ` Christoph Hellwig
2018-11-09 13:29 ` Jens Axboe
2018-11-09 13:29 ` Jens Axboe
2018-11-09 17:10 ` Sagi Grimberg
2018-11-09 17:10 ` Sagi Grimberg
2018-11-09 17:12 ` Jens Axboe
2018-11-09 17:12 ` Jens Axboe
2018-11-02 6:37 Christoph Hellwig
2018-11-02 6:37 ` Christoph Hellwig
2018-11-02 14:15 ` Jens Axboe
2018-11-02 14:15 ` 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=08296696-8fd5-1c99-1df2-39ccda11dea7@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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.