From: Randy Dunlap <rdunlap@xenotime.net>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-nfs@vger.kernel.org
Subject: Re: linux-next: Tree for Mar 6 (nfs)
Date: Tue, 13 Mar 2012 13:58:53 -0700 [thread overview]
Message-ID: <4F5FB50D.60607@xenotime.net> (raw)
In-Reply-To: <4F566E37.5040009@xenotime.net>
On 03/06/2012 12:06 PM, Randy Dunlap wrote:
> On 03/05/2012 11:07 PM, Stephen Rothwell wrote:
>
>> Hi all,
>>
>> Changes since 20120305:
>>
>> The nfs tree lost its build failure.
>
>
>
> fs/nfs/nfs4xdr.c:3438:7: error: 'nfs_debug' undeclared (first use in this function)
>
> Full randconfig file is attached.
>
This build error still occurs in linux-next 20120313.
--
~Randy
prev parent reply other threads:[~2012-03-13 20:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120306180746.25c595babf8b5072366cdbec@canb.auug.org.au>
2012-03-06 20:06 ` linux-next: Tree for Mar 6 (nfs) Randy Dunlap
2012-03-13 20:58 ` Randy Dunlap [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=4F5FB50D.60607@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).