From: Rusty Russell <rusty@rustcorp.com.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-next@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: linux-next: build failure
Date: Wed, 27 Aug 2008 12:55:22 +1000 [thread overview]
Message-ID: <200808271255.22789.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20080827100656.0f87e6b2.sfr@canb.auug.org.au>
On Wednesday 27 August 2008 10:06:56 Stephen Rothwell wrote:
> Introduced by commit 4cb9da6ecc2b0e25056b45981239475f8509d59d ("remove
> CONFIG_KMOD from net") which added a !CONFIG_MODULES (static inline)
> version of dev_load() to include/linux/netdevice.h but the copy in
> net/core/dev.c is not protected by CONFIG_MODULES.
Thanks. I've fixed this the simplest way: remove the change to the header.
Rusty.
next prev parent reply other threads:[~2008-08-27 2:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 0:06 linux-next: build failure Stephen Rothwell
2008-08-27 2:55 ` Rusty Russell [this message]
2008-08-27 4:54 ` 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=200808271255.22789.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=johannes@sipsolutions.net \
--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).