From: Arjan van de Ven <arjan@infradead.org>
To: Duncan Sands <baldrick@free.fr>
Cc: Ingo Molnar <mingo@elte.hu>, Andrew Morton <akpm@osdl.org>,
Linus Torvalds <torvalds@osdl.org>,
Jes Sorensen <jes@trained-monkey.org>,
linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: [patch 00/62] sem2mutex: -V1
Date: Fri, 13 Jan 2006 14:06:11 +0100 [thread overview]
Message-ID: <1137157571.2936.14.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <200601131400.00279.baldrick@free.fr>
On Fri, 2006-01-13 at 13:59 +0100, Duncan Sands wrote:
> > this patch-queue converts 66% of all semaphore users in 2.6.15-git9 to
> > mutexes.
>
> Hi Ingo, the changes to drivers/usb/atm/usbatm.[ch] conflict with a bunch
> of patches I just sent to Greg KH. How do you plan to handle this kind of
> thing? If you like, I can tweak this part of your patch so it applies on
> top of mine, and push it to Greg.
ideally you merge the patch into your queue and send it (via gregkh) on
its way to the final kernel.org merge.
This queue isn't meant to be "this is all going direct to linus
bypassing everyone"; we're trying to get as much as possible sent via
the maintainers. So if you as maintainer want to pick up a patch, we're
very happy about that!
Greetings,
Arjan van de Ven
next prev parent reply other threads:[~2006-01-13 13:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 12:44 Ingo Molnar
2006-01-13 12:59 ` Duncan Sands
2006-01-13 13:06 ` Arjan van de Ven [this message]
2006-01-13 13:44 ` Ingo Molnar
2006-01-13 18:25 ` Ingo Oeser
2006-01-13 19:56 ` Ingo Molnar
2006-01-13 21:04 ` Matan Peled
2006-01-13 21:25 ` Arjan van de Ven
2006-01-13 22:09 ` Junio C Hamano
2006-01-13 22:13 ` Arjan van de Ven
2006-01-14 13:22 ` Ingo Oeser
2006-01-14 13:49 ` Thomas Gleixner
2006-01-14 13:16 ` Ingo Oeser
2006-01-14 13:31 ` Arjan van de Ven
2006-01-14 13:38 ` Ingo Molnar
2006-01-13 13:23 ` Ingo Molnar
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=1137157571.2936.14.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=akpm@osdl.org \
--cc=baldrick@free.fr \
--cc=greg@kroah.com \
--cc=jes@trained-monkey.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@osdl.org \
/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
all inboxes | Powered by JetHome®