linux-kernel - Re: [GIT PULL] block driver bits for 3.7

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+55aFwLUuwue0RQn2r1EZgZL_r-wO-cjJAgpUObXKMkA7S1xQ@mail.gmail.com>
Date:	Mon, 29 Oct 2012 11:35:16 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Jens Axboe <axboe@...nel.dk>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] block driver bits for 3.7

On Mon, Oct 29, 2012 at 11:21 AM, Jens Axboe <axboe@...nel.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?

          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/