From: David Howells <dhowells@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: dhowells@redhat.com, Andrew Morton <akpm@linux-foundation.org>,
linux-next@vger.kernel.org, Prarit Bhargava <prarit@redhat.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-ia64 <linux-ia64@vger.kernel.org>,
Sam Ravnborg <sam@ravnborg.org>, Kyle McMartin <kyle@mcmartin.ca>,
Tony Luck <tony.luck@intel.com>,
Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: linux-next: build problem with nfs tree (Was: Re: [mmotm][PATCH] fix ia64 build error)
Date: Sat, 17 Jan 2009 04:43:52 +0000 [thread overview]
Message-ID: <24484.1232167432@redhat.com> (raw)
In-Reply-To: <20090116134930.68e783aa.sfr@canb.auug.org.au>
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > > I have dropped the nfs tree from linux-next for today.
> >
> > Just for this buglet? That sounds a bit savage.
>
> There was another problem with the fscache code as well. Also, this was
> reported the day before yesterday and got no response.
I've been flying to Tasmania for LCA and spending much time sitting around in
too many different airports.
> Also, the other patch that added EXPORT_SYMBOL(copy_page) "recently" was
> from December, *2007* ... Also, this is 2.6.30 material and they have a long
> time to fix it.
The patch was required Tuesday morning for my patches to build on top of
Linus's vanilla kernel. This may have changed, but I haven't checked - too
busy enjoying my pre-LCA hols in Tas:-)
David
next prev parent reply other threads:[~2009-01-17 4:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 11:05 [mmotm][PATCH] fix ia64 build error KOSAKI Motohiro
2009-01-15 17:35 ` Andrew Morton
2009-01-15 17:52 ` Luck, Tony
2009-01-16 1:49 ` linux-next: build problem with nfs tree (Was: Re: [mmotm][PATCH] fix ia64 build error) Stephen Rothwell
2009-01-16 1:59 ` Andrew Morton
2009-01-16 2:49 ` Stephen Rothwell
2009-01-16 3:41 ` KOSAKI Motohiro
2009-01-16 4:34 ` Stephen Rothwell
2009-01-16 22:15 ` Andrew Morton
2009-01-16 22:40 ` Stephen Rothwell
2009-01-16 22:49 ` Stephen Rothwell
2009-01-16 22:51 ` Andrew Morton
2009-01-17 4:43 ` David Howells [this message]
2009-01-17 5:00 ` Stephen Rothwell
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=24484.1232167432@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=kyle@mcmartin.ca \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=prarit@redhat.com \
--cc=sam@ravnborg.org \
--cc=sfr@canb.auug.org.au \
--cc=tony.luck@intel.com \
--cc=trond.myklebust@fys.uio.no \
/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