From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Ingo Molnar <mingo@elte•hu>
Cc: Randy Dunlap <randy.dunlap@oracle•com>,
Arnd Bergmann <arnd@arndb•de>,
linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
Al Viro <viro@zeniv•linux.org.uk>,
Peter Osterlund <petero2@telia•com>,
Jens Axboe <jens.axboe@oracle•com>,
Akinobu Mita <akinobu.mita@gmail•com>
Subject: Re: [PATCH -next] pktcdvd: improve BKL and compat_ioctl.c usage
Date: Wed, 3 Mar 2010 10:38:10 +1100 [thread overview]
Message-ID: <20100303103810.02c2fd63.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20100302120621.GA28192@elte.hu>
[-- Attachment #1: Type: text/plain, Size: 338 bytes --]
Hi Ingo,
On Tue, 2 Mar 2010 13:06:21 +0100 Ingo Molnar <mingo@elte•hu> wrote:
>
> FYI, this build bug now triggers upstream too - none of the fixes was applied.
Thanks again, I have put Arnd's patch in my fixes as well.
--
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-03-02 23:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 7:35 linux-next: Tree for February 25 Stephen Rothwell
2010-02-25 17:21 ` linux-next: Tree for February 25 (quota) Randy Dunlap
2010-03-01 13:27 ` Jan Kara
2010-03-01 16:56 ` Randy Dunlap
2010-02-25 17:55 ` [PATCH -next] staging: fix wlan-ng printk format warning Randy Dunlap
2010-02-25 17:55 ` [PATCH -next] fs: fix compat_ioctl when CONFIG_BLOCK=n Randy Dunlap
2010-02-25 21:27 ` [PATCH -next] pktcdvd: improve BKL and compat_ioctl.c usage Arnd Bergmann
2010-02-25 22:10 ` Randy Dunlap
2010-03-02 12:06 ` Ingo Molnar
2010-03-02 23:38 ` Stephen Rothwell [this message]
2010-02-25 22:41 ` [PATCH -next] staging/pohmelfs: fix write_inode parameter warning Randy Dunlap
2010-02-26 0:41 ` Stephen Rothwell
2010-03-07 9:22 ` Geert Uytterhoeven
2010-03-07 15:50 ` Greg KH
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=20100303103810.02c2fd63.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akinobu.mita@gmail$(echo .)com \
--cc=arnd@arndb$(echo .)de \
--cc=jens.axboe@oracle$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@elte$(echo .)hu \
--cc=petero2@telia$(echo .)com \
--cc=randy.dunlap@oracle$(echo .)com \
--cc=viro@zeniv$(echo .)linux.org.uk \
/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