linux-kernel - Re: [GIT PULL] percpu for 2.6.31

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Thu, 18 Jun 2009 14:39:59 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	tj@...nel.org, mingo@...e.hu, linux-kernel@...r.kernel.org,
	kyle@...artin.ca
Subject: Re: [GIT PULL] percpu for 2.6.31

On Thu, 18 Jun 2009 14:22:20 -0700 (PDT)
Linus Torvalds <torvalds@...ux-foundation.org> wrote:

> On Thu, 18 Jun 2009, Tejun Heo wrote:
> > 
> > Please pull from percpu-for-linus git tree from:
> > 
> >     git://git.kernel.org/pub/scm/linux/kernel/git/tj/percpu.git for-linus
> 
> I'm very unhappy with this kind of crap.

AFACIT none of these patches have ever been in linux-next.  Half or
more of them turned up on the mailing list for the first time two days
ago and there's little evidence that anyone has even looked at them.

If this doesn't mean "you missed 2.6.31" then what does?



Yes, things like this can be messy and hard to develop and maintain
outside the merge window.  We understand this.  There are special
cases.  But when this happens, let's talk about it and see what we can
do!  Please let's not pretend that this is an ordinary old git merge
like all the others.
--
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/