From: Arnd Bergmann <arnd@arndb.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Frederic Weisbecker" <fweisbec@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
"Márton Németh" <nm127@freemail.hu>,
"H. Peter Anvin" <hpa@zytor.com>, "Ian Kent" <raven@themaw.net>
Subject: Re: [PATCH 1/2] autofs: Only declare function when CONFIG_COMPAT is defined
Date: Mon, 4 Oct 2010 10:26:42 +0200 [thread overview]
Message-ID: <201010041026.42385.arnd@arndb.de> (raw)
In-Reply-To: <20100927123252.8e1826e8.akpm@linux-foundation.org>
On Monday 27 September 2010 21:32:52 Andrew Morton wrote:
> > My initial reaction was to put these into my bkl/vfs tree, but then I noticed
> > that they are against a 2.6.36 bug. Who's taking care of getting them upstream?
> >
> > - Ian (maintainer)
> > - Arnd (who wrote the broken patch to start with)
> > - Frederic (who pushed the broken patch to Linus)
> > - Andrew (took them into -mm)
> >
> > I don't care either way, just trying to make sure it gets there and we don't
> > all submit the same patch simultaneously.
>
> The usual deal: if it turns up in linux-next then I drop it. If it
> doesn't then I'll merge it into 2.6.37.
I ended up putting them into my bkl/vfs tree after all now.
Arnd
next prev parent reply other threads:[~2010-10-04 8:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-24 13:22 [PATCH 1/2] autofs: Only declare function when CONFIG_COMPAT is defined Frederic Weisbecker
2010-09-24 13:22 ` [PATCH 2/2] autofs4: " Frederic Weisbecker
2010-09-25 15:55 ` [PATCH 1/2] autofs: " Arnd Bergmann
2010-09-26 13:02 ` Frederic Weisbecker
2010-09-27 19:32 ` Andrew Morton
2010-10-04 8:26 ` Arnd Bergmann [this message]
2010-09-30 20:00 ` Geert Uytterhoeven
2010-09-30 20:20 ` H. Peter Anvin
2010-09-30 20:37 ` Geert Uytterhoeven
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=201010041026.42385.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nm127@freemail.hu \
--cc=raven@themaw.net \
/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