From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Netdev <netdev@vger.kernel.org>
Subject: Re: linux-next: Tree for March 22 (net-sysfs.c)
Date: Mon, 22 Mar 2010 08:31:09 -0700 [thread overview]
Message-ID: <4BA78D3D.9090007@oracle.com> (raw)
In-Reply-To: <20100322171937.d753bdba.sfr@canb.auug.org.au>
On 03/21/10 23:19, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20100319:
>
>
> The net tree lost its build failures.
When CONFIG_SYSFS is not enabled:
net/core/net-sysfs.c:742: error: implicit declaration of function 'rx_queue_remove_kobjects'
net/core/net-sysfs.c:783: error: implicit declaration of function 'rx_queue_register_kobjects'
--
~Randy
next prev parent reply other threads:[~2010-03-22 15:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100322171937.d753bdba.sfr@canb.auug.org.au>
2010-03-22 9:10 ` -next Mar 22: s390 build failure (drivers/s390/net/qeth_l3) Sachin Sant
2010-03-22 13:00 ` Blaschka
2010-03-22 17:00 ` David Miller
2010-03-22 15:31 ` Randy Dunlap [this message]
2010-03-22 17:22 ` linux-next: Tree for March 22 (net-sysfs.c) David Miller
2010-03-22 20:48 ` Eric Dumazet
2010-03-23 1:05 ` David Miller
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=4BA78D3D.9090007@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@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).