From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Woodhouse <dwmw2@infradead.org>
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 18:28:53 +1100 [thread overview]
Message-ID: <20151015182853.2d770f13@canb.auug.org.au> (raw)
In-Reply-To: <1444892095.125804.210.camel@infradead.org>
Hi David,
On Thu, 15 Oct 2015 07:54:55 +0100 David Woodhouse <dwmw2@infradead.org> wrote:
>
> 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.
Thanks, I will drop the patch now.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
prev parent reply other threads:[~2015-10-15 7:28 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
2015-10-15 7:28 ` Stephen Rothwell [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=20151015182853.2d770f13@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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