From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] block driver bits for 3.7
Date: Mon, 29 Oct 2012 20:13:34 +0100 [thread overview]
Message-ID: <508ED55E.4000308@kernel.dk> (raw)
In-Reply-To: <CA+55aFwLUuwue0RQn2r1EZgZL_r-wO-cjJAgpUObXKMkA7S1xQ@mail.gmail.com>
On 2012-10-29 19:35, Linus Torvalds wrote:
> On Mon, Oct 29, 2012 at 11:21 AM, Jens Axboe <axboe@kernel.dk> wrote:
>>
>> Later than I would have liked, but I was traveling around the merge
>> window and then a fixes snuck in past that and I wanted to ensure that
>> everything was fully baked again.
>
> Didn't we agree last time that drbd just wasn't important enough to
> *constantly* cause these kinds of "lots of late fixes"?
>
> In fact, they aren't even fixes. There's a single small commit during
> the merge window since v3.6 touching that driver, and it wasn't even
> drbd-specific.
>
> In other words, I see absolutely no reason to pull this stuff at this
> time. It's so far out of the merge window that it's not funny, and it
> has absolutely nothing about it that says "fixes".
>
> So mind sending just the actual *fixes* for actual regressions, and
> then you can re-push this for the next merge window?
It was actually the floppy part that caused a delay on my end. But sure,
I can distill this down given the time. I'll send out a new one
tomorrow.
--
Jens Axboe
next prev parent reply other threads:[~2012-10-29 19:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 18:21 [GIT PULL] block driver bits for 3.7 Jens Axboe
2012-10-29 18:35 ` Linus Torvalds
2012-10-29 19:13 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-30 13:25 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=508ED55E.4000308@kernel.dk \
--to=axboe@kernel.dk \
--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 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).