All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Jens Axboe <axboe@fb.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-block@vger.kernel.org
Subject: Re: [GIT PULL] Block fixes for 4.5-final
Date: Thu, 3 Mar 2016 14:13:53 -0700	[thread overview]
Message-ID: <56D8A911.10606@kernel.dk> (raw)
In-Reply-To: <CA+55aFxOmimDRNTwyQdve=WBrCzdX-TMTSLjqpo+v7P8t2pN0Q@mail.gmail.com>

On 03/03/2016 02:11 PM, Linus Torvalds wrote:
> On Thu, Mar 3, 2016 at 12:57 PM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
>>
>> Feel free to resend the parts that are actually critical, but explain
>> exactly why they are so critical when you do.
>
> Just to clarify: anything that contains "lightnvm" is definitely not
> critical enough. Are there even any users? I'm done seeing these
> constant large lightnvm patches.

Right, see previous email, that can surely be pulled. But at the same 
time, it's not exactly high impact stuff. That said, it should have gone 
to 4.6 originally.

> NVMe is certainly a lot more important, but if it's about hot unplug
> that has never been reliable before, or about cleaning up the reset
> sequence by avoiding unmapping the register space, I really don't see
> what makes those critical patches that should go in outside of the
> merge window.

Fair enough.

> So no more of this "several hundred lines of random code changes after
> rc6 for issues that aren't fixing an actual critical bug and has never
> worked before either".

I'll run a tighter ship for post-merge window.

> The block pull request was literally three times the size of all the
> other (*seven*) pull requests I've done today that were actually small
> fixes. Yeah, I'm not going to say that all of those were necessarily
> truly critical either, but at least they were very small and clearly
> fixes, and several of them fixed things like actual BUG_ON's or boot
> hangs.

I could have split it in 3? :-)

-- 
Jens Axboe

  reply	other threads:[~2016-03-03 21:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-03 17:25 [GIT PULL] Block fixes for 4.5-final Jens Axboe
2016-03-03 20:57 ` Linus Torvalds
2016-03-03 21:11   ` Linus Torvalds
2016-03-03 21:13     ` Jens Axboe [this message]
2016-03-03 21:11   ` Jens Axboe
2016-03-03 21:20     ` Linus Torvalds
2016-03-03 21:28       ` Jens Axboe
2016-03-03 21:53         ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2016-03-04 22:02 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=56D8A911.10606@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=axboe@fb.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.