From: Jens Axboe <axboe@kernel.dk>
To: David Woodhouse <dwmw2@infradead.org>
Cc: joro@8bytes.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: dmar compile failure in -git
Date: Tue, 20 Oct 2020 11:12:42 -0600 [thread overview]
Message-ID: <90feb2ec-95c4-ddd6-4378-8ef56ddd2b5e@kernel.dk> (raw)
In-Reply-To: <5646206e-ca52-4b1f-6182-4cb760ba712a@kernel.dk>
On 10/20/20 10:26 AM, Jens Axboe wrote:
> On Sat, Oct 17, 2020 at 1:03 AM David Woodhouse <dwmw2@infradead.org> wrote:
>> On 16 October 2020 22:23:46 BST, Jens Axboe <axboe@kernel.dk> wrote:
>>> Hi,
>>>
>>> Ran into this one yesterday:
>>>
>>> drivers/iommu/intel/dmar.c: In function ‘free_iommu’:
>>> drivers/iommu/intel/dmar.c:1139:41: error: ‘struct iommu_device’ has no
>>> member named ‘ops’
>>> 1139 | if (intel_iommu_enabled && iommu->iommu.ops) {
>>> | ^
>>> make[3]: *** [scripts/Makefile.build:283: drivers/iommu/intel/dmar.o]
>>> Error 1
>>> make[3]: *** Waiting for unfinished jobs....
>>> make[2]: *** [scripts/Makefile.build:500: drivers/iommu/intel] Error 2
>>> make[1]: *** [scripts/Makefile.build:500: drivers/iommu] Error 2
>>> make: *** [Makefile:1777: drivers] Error 2
>>>
>>> which is due to the config I use:
>>
>> Thanks. Should be fixed by
>> https://www.mail-archive.com/iommu@lists.linux-foundation.org/msg45697.html
>
> Can we please get this known build breakage fix upstream? It keeps
> breaking my test box compiles, which is pretty annoying.
Nevermind, looks like it went upstream about the same time as I sent
this email. Thanks!
--
Jens Axboe
prev parent reply other threads:[~2020-10-20 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 21:23 Jens Axboe
2020-10-17 7:03 ` David Woodhouse
2020-10-20 16:26 ` Jens Axboe
2020-10-20 17:12 ` Jens Axboe [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=90feb2ec-95c4-ddd6-4378-8ef56ddd2b5e@kernel.dk \
--to=axboe@kernel.dk \
--cc=dwmw2@infradead.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome