From: Linus Torvalds <torvalds@linux-foundation.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block <linux-block@vger.kernel.org>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] block: remove CONFIG_LBDAF
Date: Sat, 6 Apr 2019 06:30:48 -1000 [thread overview]
Message-ID: <CAHk-=whUmB7ine4==Z1L4csYCYaQM8-catk8ytNsnyPTs5uwZw@mail.gmail.com> (raw)
In-Reply-To: <20190405160859.5288-1-hch@lst.de>
On Fri, Apr 5, 2019 at 6:09 AM Christoph Hellwig <hch@lst.de> wrote:
>
> Dropping this option removes a somewhat weird non-default config that
> has cause various bugs or compiler warnings when actually used.
I'm ok with this, but let's queue it for 5.2, ok? Jens?
Linus
next prev parent reply other threads:[~2019-04-06 16:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 16:08 [PATCH] block: remove CONFIG_LBDAF Christoph Hellwig
2019-04-05 18:00 ` Jens Axboe
2019-04-06 16:30 ` Linus Torvalds [this message]
2019-04-06 16:48 ` Jens Axboe
2019-04-08 8:30 ` Hannes Reinecke
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='CAHk-=whUmB7ine4==Z1L4csYCYaQM8-catk8ytNsnyPTs5uwZw@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@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).