From: Ingo Molnar <mingo@elte.hu>
To: Patrick McHardy <kaber@trash.net>
Cc: Andrew Morton <akpm@osdl.org>,
Harald Welte <laforge@netfilter.org>,
coreteam@netfilter.org, linux-kernel@vger.kernel.org,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: [netfilter-core] [patch 2.6.15-mm4] sem2mutex: netfilter x_table.c
Date: Wed, 18 Jan 2006 09:15:27 +0100 [thread overview]
Message-ID: <20060118081527.GB2324@elte.hu> (raw)
In-Reply-To: <43CDA834.3070301@trash.net>
* Patrick McHardy <kaber@trash.net> wrote:
> Ingo Molnar wrote:
> >From: Ingo Molnar <mingo@elte.hu>
> >
> >semaphore to mutex conversion.
> >
> >the conversion was generated via scripts, and the result was validated
> >automatically via a script as well.
>
> I haven't followed all the mutex patches, is this intended
> for mainline or for -mm?
best would be if you could pick the patches up (if they look good to
you, and if they pass testing with CONFIG_DEBUG_MUTEXES enabled), and
thus they would flow upstream once you did a merge with Andrew or Linus
next time around.
we'll still keep them in -mm, just to get early feedback (and to make
sure nothing is dropped on the floor), but the ultimate merging should
happen via maintainers. [so that the mutex patches impact maintainer's
workflow and their pending patches in the least minimal way.] If things
clash with our mutex migration changes in -mm, we'll redo the affected
-mm mutex patches whenever Andrew pulls a maintainer tree.
Ingo
prev parent reply other threads:[~2006-01-18 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-14 14:30 Ingo Molnar
2006-01-14 14:36 ` [patch 2.6.15-mm4] sem2mutex: autofs4 wq_sem Ingo Molnar
2006-01-18 2:30 ` [netfilter-core] [patch 2.6.15-mm4] sem2mutex: netfilter x_table.c Patrick McHardy
2006-01-18 2:46 ` Andrew Morton
2006-01-18 8:15 ` Ingo Molnar [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=20060118081527.GB2324@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=coreteam@netfilter.org \
--cc=kaber@trash.net \
--cc=laforge@netfilter.org \
--cc=linux-kernel@vger.kernel.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®