public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Diana Craciun OSS <diana.craciun@oss•nxp.com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
	Alex Williamson <alex.williamson@redhat•com>
Cc: Bharat Bhushan <Bharat.Bhushan@nxp•com>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build failure after merge of the vfio tree
Date: Tue, 13 Oct 2020 18:56:07 +0300	[thread overview]
Message-ID: <276bf3f3-108b-fe60-4d17-d3f314e61db4@oss.nxp.com> (raw)
In-Reply-To: <20201013140744.64937ecd@canb.auug.org.au>

Hi,

How does it fail? What's the error?

Thanks,
Diana


On 10/13/2020 6:07 AM, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the vfio tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> 
> Caused by commit
> 
>    cc0ee20bd969 ("vfio/fsl-mc: trigger an interrupt via eventfd")
>    ac93ab2bf69a ("vfio/fsl-mc: Add support for device reset")
> 
> I have used the vfio tree from next-20201012 for today.
> 


  reply	other threads:[~2020-10-13 15:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-13  3:07 linux-next: build failure after merge of the vfio tree Stephen Rothwell
2020-10-13 15:56 ` Diana Craciun OSS [this message]
2020-10-13 19:20   ` Alex Williamson
2020-10-15  0:59     ` Stephen Rothwell
2020-10-15  2:21       ` Alex Williamson
2020-10-13 22:16   ` Stephen Rothwell
2020-10-14 13:43     ` Diana Craciun OSS
  -- strict thread matches above, loose matches on Subject: below --
2026-02-09  2:07 Mark Brown
2026-02-09  2:42 ` Mark Brown
2026-02-09  9:46   ` Edward Srouji
2026-02-09  6:30 ` Leon Romanovsky

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=276bf3f3-108b-fe60-4d17-d3f314e61db4@oss.nxp.com \
    --to=diana.craciun@oss$(echo .)nxp.com \
    --cc=Bharat.Bhushan@nxp$(echo .)com \
    --cc=alex.williamson@redhat$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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