From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Arnd Bergmann <arnd@arndb•de>
Cc: "\"Frédéric Weisbecker\"" <fweisbec@gmail•com>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
"Linus Torvalds" <torvalds@linux-foundation•org>
Subject: Re: linux-next: manual merge of the bkl-ioctl tree with my fixes tree
Date: Wed, 28 Apr 2010 16:22:09 +1000 [thread overview]
Message-ID: <20100428162209.cc9b2487.sfr@canb.auug.org.au> (raw)
In-Reply-To: <201004271102.35904.arnd@arndb.de>
[-- Attachment #1: Type: text/plain, Size: 735 bytes --]
Hi Arndt,
On Tue, 27 Apr 2010 11:02:35 +0200 Arnd Bergmann <arnd@arndb•de> wrote:
>
> It's not clear yet how we do it. Ideally "pktcdvd: improve BKL and
> compat_ioctl.c usage" should find its way into -rc1 in some way, but
> we need to reshuffle the BKL removal trees to make that go in nicely.
>
> Where is your fixes tree? Maybe Frederic can take all BKL related
> patches from that into one of his trees.
My fixes tree is here: ssh://master.kernel.org/~sfr/next-fixes.git it
currently only contains your pktcdvd patch. My understanding was that
this patch was a fix for a build problem with Linus' tree.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-04-28 6:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 5:06 linux-next: manual merge of the bkl-ioctl tree with my fixes tree Stephen Rothwell
2010-04-27 9:02 ` Arnd Bergmann
2010-04-28 6:22 ` Stephen Rothwell [this message]
2010-04-28 12:36 ` [PATCH] pktcdvd: improve BKL and compat_ioctl.c usage Arnd Bergmann
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=20100428162209.cc9b2487.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=arnd@arndb$(echo .)de \
--cc=fweisbec@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=torvalds@linux-foundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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