From: Andi Kleen <ak@linux.intel.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kbuild@vger.kernel.org
Subject: Re: linux-next: build warnings after merge of the modules tree
Date: Tue, 5 Nov 2013 06:17:02 -0800 [thread overview]
Message-ID: <20131105141702.GE1962@tassilo.jf.intel.com> (raw)
In-Reply-To: <87fvrba8su.fsf@rustcorp.com.au>
> modpost creates an entry when it sees the CRC, then when it sees the
> actual symbol, it complains that it's seen it before. The preloaded
> flag already exists for the equivalent case where we loaded from
> Module.symvers, so use that.
Looks good. Thanks for fixing.
-Andi
next prev parent reply other threads:[~2013-11-05 14:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 2:41 linux-next: build warnings after merge of the modules tree Stephen Rothwell
2013-11-05 2:20 ` Rusty Russell
2013-11-05 14:17 ` Andi Kleen [this message]
2013-11-05 23:07 ` 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=20131105141702.GE1962@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--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).