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]
Message-ID: <20080426155939.GQ14990@parisc-linux.org>
Date:	Sat, 26 Apr 2008 09:59:39 -0600
From:	Matthew Wilcox <matthew@....cx>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Announce: Semaphore-Removal tree

On Sat, Apr 26, 2008 at 11:54:39PM +1000, Stephen Rothwell wrote:
> Hi Willy,
> 
> On Fri, 25 Apr 2008 11:00:21 -0600 Matthew Wilcox <matthew@....cx> wrote:
> >
> > Stephen, could you pick these patches up for linux-next?
> > 
> > git://git.kernel.org/pub/scm/linux/kernel/git/willy/misc.git semaphore-removal
> 
> This is in addition to the semaphore branch? Should it go before or after
> that i.e. does it depend on it?

It's in addition to, and it's independent of it.  I don't intend to
create any conflicts or dependencies between them.  In case I do ...
let's say semaphore-removal goes after semaphore.

-- 
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ