From: Alex Williamson <alex.williamson@redhat.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Kirti Wankhede <kwankhede@nvidia.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Cornelia Huck <cohuck@redhat.com>, KVM <kvm@vger.kernel.org>
Subject: Re: linux-next: Tree for Jun 2 (vfio)
Date: Tue, 2 Jun 2020 13:56:04 -0600 [thread overview]
Message-ID: <20200602135604.21081784@x1.home> (raw)
In-Reply-To: <20200602091615.145e6f09@x1.home>
On Tue, 2 Jun 2020 09:16:15 -0600
Alex Williamson <alex.williamson@redhat.com> wrote:
> On Tue, 2 Jun 2020 07:36:45 -0700
> Randy Dunlap <rdunlap@infradead.org> wrote:
>
> > On 6/2/20 3:37 AM, Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > News: The merge window has opened, so please do *not* add v5.9 material
> > > to your linux-next included branches until after v5.8-rc1 has been
> > > released.
> > >
> > > Changes since 20200529:
> > >
> >
> > on i386:
> >
> > ld: drivers/vfio/vfio_iommu_type1.o: in function `vfio_dma_populate_bitmap':
> > vfio_iommu_type1.c:(.text.unlikely+0x41): undefined reference to `__udivdi3'
>
> I think Kirti received a 0-day report on this. Kirti, could you please
> post the fix you identified? Thanks,
This should be resolved in the next refresh. Thanks,
Alex
next prev parent reply other threads:[~2020-06-02 19:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 10:37 linux-next: Tree for Jun 2 Stephen Rothwell
2020-06-02 14:36 ` linux-next: Tree for Jun 2 (vfio) Randy Dunlap
2020-06-02 15:16 ` Alex Williamson
2020-06-02 19:56 ` Alex Williamson [this message]
2020-06-02 15:18 ` linux-next: Tree for Jun 2 (x86/xen) Randy Dunlap
2020-06-02 21:47 ` Boris Ostrovsky
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=20200602135604.21081784@x1.home \
--to=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.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