From: Mark Brown <broonie@kernel.org>
To: Will Deacon <will.deacon@arm.com>
Cc: "Krzysztof Kozłowski" <k.kozlowski@samsung.com>,
"Joerg Roedel" <joro@8bytes.org>,
"Catalin Marinas" <Catalin.Marinas@arm.com>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] iommu/exynos: Fix arm64 allmodconfig build
Date: Mon, 15 Dec 2014 15:56:15 +0000 [thread overview]
Message-ID: <20141215155615.GD11764@sirena.org.uk> (raw)
In-Reply-To: <20141215153804.GK20738@arm.com>
[-- Attachment #1: Type: text/plain, Size: 536 bytes --]
On Mon, Dec 15, 2014 at 03:38:04PM +0000, Will Deacon wrote:
> On Mon, Dec 15, 2014 at 03:35:29PM +0000, Mark Brown wrote:
> > I don't mind either way, it just seemed to be easier to report the bug
> > with a patch. If Jeorg is busy perhaps it can go via the arm64 tree,
> > the issue is triggered by the addition of the platform there?
> Can I pass the buck to arm-soc, as they're handling arm64 platform code?
> It seems sensible to merge the fix via the same tree that introduced the
> breakage.
Sure, just resending to them...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-12-15 15:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 13:00 [PATCH] iommu/exynos: Fix arm64 allmodconfig build Mark Brown
2014-12-15 13:10 ` Krzysztof Kozłowski
2014-12-15 15:35 ` Mark Brown
[not found] ` <20141215153529.GC11764-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-12-15 15:38 ` Will Deacon
2014-12-15 15:56 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-12-15 15:54 Mark Brown
2014-12-16 20:40 ` Arnd Bergmann
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=20141215155615.GD11764@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Catalin.Marinas@arm.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=k.kozlowski@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=will.deacon@arm.com \
/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