linux-kernel - Re: [PATCH 11/12] Generic semaphore implementation

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:	Fri, 29 Feb 2008 08:14:22 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
cc:	Matthew Wilcox <matthew@....cx>, Ingo Molnar <mingo@...e.hu>,
	linux-kernel@...r.kernel.org,
	Matthew Wilcox <willy@...ux.intel.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-next@...r.kernel.org
Subject: Re: [PATCH 11/12] Generic semaphore implementation



On Fri, 29 Feb 2008, Stephen Rothwell wrote:
>
> On Thu, 28 Feb 2008 17:39:54 -0700 Matthew Wilcox <matthew@....cx> wrote:
> >
> > Stephen, I've put the semaphore patches into a git tree; can you add it
> > to linux-next?
> > 
> > http://git.kernel.org/?p=linux/kernel/git/willy/misc.git;a=shortlog;h=semaphore
> 
> I have put this in for toady's build (but using the git URL).  This tree
> is in the "too many conflicts and its out until fixed" category ...
> However, it is also a candidate for Linus' "next" branch (if he is going
> to run one ...).

I'm not going to do a "next" branch just for stupid syntactic merge errors 
that are trivially fixed due to some include-file moving. If 
submaintainers can fix it up trivially, it's really not worth it. 

				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/