From: Randy Dunlap <rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public•gmane.org>
To: Randy Dunlap <rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public•gmane.org>
Cc: Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public•gmane.org>,
linux-next-u79uwXL29TY76Z2rM5mHXA@public•gmane.org,
LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public•gmane.org>,
linux-nfs-u79uwXL29TY76Z2rM5mHXA@public•gmane.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-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
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
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public•gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-03-13 20:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 7:07 linux-next: Tree for Mar 6 Stephen Rothwell
2012-03-06 18:51 ` linux-next: Tree for Mar 6 (staging/iio) Randy Dunlap
[not found] ` <4F565CB0.8070301-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
2012-03-06 19:43 ` [PATCH] staging:iio: Fix compile error without CONFIG_DEBUG_FS Lars-Peter Clausen
[not found] ` <1331063025-25242-1-git-send-email-lars-Qo5EllUWu/uELgA04lAiVw@public.gmane.org>
2012-03-06 20:03 ` Randy Dunlap
2012-03-06 20:06 ` linux-next: Tree for Mar 6 (nfs) Randy Dunlap
[not found] ` <4F566E37.5040009-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
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-/uha2rfvqtnk1umjsbkqmq@public$(echo .)gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=linux-next-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=sfr-3FnU+UHB4dNDw9hX6IcOSA@public$(echo .)gmane.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