From: Andrew Morton <akpm@osdl.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org,
arjan@infradead.org, nico@cam.org, jes@trained-monkey.org,
viro@ftp.linux.org.uk, oleg@tv-sign.ru, dhowells@redhat.com,
alan@lxorguk.ukuu.org.uk, hch@infradead.org, ak@suse.de,
rmk+lkml@arm.linux.org.uk
Subject: Re: [patch 17/21] mutex subsystem, semaphore to mutex: automatic conversion of simpler cases
Date: Fri, 6 Jan 2006 17:30:22 -0800 [thread overview]
Message-ID: <20060106173022.3df929dd.akpm@osdl.org> (raw)
In-Reply-To: <20060107010749.GA6267@elte.hu>
Ingo Molnar <mingo@elte.hu> wrote:
>
>
> * Andrew Morton <akpm@osdl.org> wrote:
>
> > I think I'll duck this one for now.
> >
> > Perhaps it should be split up a bit?
>
> yeah, i'll merge it tomorrow and will split it up into per-driver
> patches. Could you upload an x.bz2 i should merge against - or is
> Linus-curr OK?
>
The old x.bz2 would be better please, because I'm going to have to do
fixups for various -mm-only things like dlm, asfs, reiser4, etc.
http://www.zip.com.au/~akpm/linux/patches/stuff/up-to-mutex-series.bz2
Is everything up to and including the mutex series. That's a suitable
insertion point for new stuff.
http://www.zip.com.au/~akpm/linux/patches/stuff/everything.bz2 is the whole
kit. It includes additional things which'll need fixups if you're feeling
keen.
Sorry for the hassle - there are still great gobs of stuff to merge, and
we're basically twiddling thumbs until things like nfs, powerpc, usb get
merged.
prev parent reply other threads:[~2006-01-07 1:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060105153903.GR31013@elte.hu>
2006-01-07 1:01 ` [patch 17/21] mutex subsystem, semaphore to mutex: automatic conversion of simpler cases Andrew Morton
2006-01-07 1:07 ` Ingo Molnar
2006-01-07 1:30 ` Andrew Morton [this message]
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=20060106173022.3df929dd.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--cc=jes@trained-monkey.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nico@cam.org \
--cc=oleg@tv-sign.ru \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=torvalds@osdl.org \
--cc=viro@ftp.linux.org.uk \
/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