From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the swiotlb tree
Date: Tue, 3 Jan 2017 19:11:38 -0500 [thread overview]
Message-ID: <20170104001138.GA22030@char.us.oracle.com> (raw)
In-Reply-To: <20170104105749.6f305c35@canb.auug.org.au>
On Wed, Jan 04, 2017 at 10:57:49AM +1100, Stephen Rothwell wrote:
> Hi Konrad,
>
> After merging the swiotlb tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> net/bridge/br_input.o: In function `.swiotlb_max_segment':
> (.text+0x780): multiple definition of `.swiotlb_max_segment'
> net/bridge/br.o:br.c:(.text+0x3c0): first defined here
>
> and many, many more :-(
> Caused by commit
>
> f196f1294fd2 ("swiotlb: Export swiotlb_max_segment to users")
>
> Forgotten "static nline" in include/linux/swiotlb.h ...
Duh!
Fixed it up and pushed the fix in. Thanks!
>
> I have used the swiotlb tree from next-20170103 for today.
>
> --
> Cheers,
> Stephen Rothwell
prev parent reply other threads:[~2017-01-04 0:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 23:57 linux-next: build failure after merge of the swiotlb tree Stephen Rothwell
2017-01-04 0:11 ` Konrad Rzeszutek Wilk [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=20170104001138.GA22030@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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).