From: "Roedel, Joerg" <Joerg.Roedel@amd.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
Stephen Rothwell <sfr@canb.auug.org.au>,
iommu@lists.linux-foundation.org, linux-next@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Sept 24 (iommu)
Date: Tue, 25 Sep 2012 12:16:28 +0200 [thread overview]
Message-ID: <20120925101628.GX2505@amd.com> (raw)
In-Reply-To: <1348543405.2320.146.camel@ul30vt.home>
On Mon, Sep 24, 2012 at 09:23:25PM -0600, Alex Williamson wrote:
> On Mon, 2012-09-24 at 15:02 -0700, Randy Dunlap wrote:
> > On 09/24/2012 07:53 AM, Stephen Rothwell wrote:
> >
> > > Hi all,
> > >
> > > Today was a train wreck, with lots of new conflicts across several trees
> > > and a few build failures as well.
> > >
> > > Changes since 201209021:
> > >
> >
> >
> >
> > on i386:
> >
> > drivers/built-in.o: In function `iommu_group_remove_device':
> > (.text+0x74cb10): multiple definition of `iommu_group_remove_device'
> > arch/x86/built-in.o:(.text+0x140d0): first defined here
> ...
>
>
> Here's a patch to get it past this. It still doesn't fully build, but
> the rest isn't iommu related. Thanks,
Applied, thanks.
--
AMD Operating System Research Center
Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach
General Managers: Alberto Bozzo
Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632
WARNING: multiple messages have this Message-ID (diff)
From: "Roedel, Joerg" <Joerg.Roedel@amd.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
Stephen Rothwell <sfr@canb.auug.org.au>,
<iommu@lists.linux-foundation.org>, <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Sept 24 (iommu)
Date: Tue, 25 Sep 2012 12:16:28 +0200 [thread overview]
Message-ID: <20120925101628.GX2505@amd.com> (raw)
In-Reply-To: <1348543405.2320.146.camel@ul30vt.home>
On Mon, Sep 24, 2012 at 09:23:25PM -0600, Alex Williamson wrote:
> On Mon, 2012-09-24 at 15:02 -0700, Randy Dunlap wrote:
> > On 09/24/2012 07:53 AM, Stephen Rothwell wrote:
> >
> > > Hi all,
> > >
> > > Today was a train wreck, with lots of new conflicts across several trees
> > > and a few build failures as well.
> > >
> > > Changes since 201209021:
> > >
> >
> >
> >
> > on i386:
> >
> > drivers/built-in.o: In function `iommu_group_remove_device':
> > (.text+0x74cb10): multiple definition of `iommu_group_remove_device'
> > arch/x86/built-in.o:(.text+0x140d0): first defined here
> ...
>
>
> Here's a patch to get it past this. It still doesn't fully build, but
> the rest isn't iommu related. Thanks,
Applied, thanks.
--
AMD Operating System Research Center
Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach
General Managers: Alberto Bozzo
Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2012-09-25 10:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 14:53 linux-next: Tree for Sept 24 Stephen Rothwell
2012-09-24 15:39 ` linux-next: Tree for Sept 24 (irqchip) Randy Dunlap
2012-09-24 16:07 ` Stephen Rothwell
2012-09-24 16:07 ` Stephen Rothwell
2012-09-24 16:07 ` Stephen Rothwell
2012-09-24 16:42 ` Stephen Warren
2012-09-24 16:42 ` Stephen Warren
2012-09-24 16:46 ` Olof Johansson
2012-09-24 16:46 ` Olof Johansson
2012-11-03 1:47 ` Randy Dunlap
2012-11-03 1:47 ` Randy Dunlap
2012-09-24 19:50 ` linux-next: Tree for Sept 24 (net/ipv4) Randy Dunlap
2012-09-24 22:02 ` linux-next: Tree for Sept 24 (iommu) Randy Dunlap
2012-09-25 3:23 ` Alex Williamson
2012-09-25 10:16 ` Roedel, Joerg [this message]
2012-09-25 10:16 ` Roedel, Joerg
2012-09-24 22:10 ` linux-next: Tree for Sept 24 (remoteproc) Randy Dunlap
2012-09-30 8:33 ` Ohad Ben-Cohen
2012-10-01 23:16 ` Randy Dunlap
2012-10-02 8:04 ` Ohad Ben-Cohen
2012-09-24 22:25 ` linux-next: Tree for Sept 24 (net without INET) Randy Dunlap
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=20120925101628.GX2505@amd.com \
--to=joerg.roedel@amd.com \
--cc=alex.williamson@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.