From: David Woodhouse <dwmw2@infradead.org>
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 dwmw2-iommu tree
Date: Thu, 15 Oct 2015 07:54:55 +0100 [thread overview]
Message-ID: <1444892095.125804.210.camel@infradead.org> (raw)
In-Reply-To: <20151015135500.5fe9af8f@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 574 bytes --]
On Thu, 2015-10-15 at 13:55 +1100, Stephen Rothwell wrote:
>
> Ping?
>
> Of course my patch did not apply today since the kref has now
> vanished in a rebase ...
The problem which required said patch should also be gone, though —
CONFIG_INTEL_IOMMU_SVM now selects CONFIG_MMU_NOTIFIER, and its data
structures are guarded with #ifdef CONFIG_INTEL_IOMMU_SVM.
Apologies for the lack of an explicit response (other than the implicit
one of fixing the problem). It should have occurred to me that you'd be
trying to carry the patch forward.
--
dwmw2
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5691 bytes --]
next prev parent reply other threads:[~2015-10-15 6:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 7:32 linux-next: build failure after merge of the dwmw2-iommu tree Stephen Rothwell
2015-10-15 2:55 ` Stephen Rothwell
2015-10-15 6:54 ` David Woodhouse [this message]
2015-10-15 7:28 ` Stephen Rothwell
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=1444892095.125804.210.camel@infradead.org \
--to=dwmw2@infradead.org \
--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