From: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Daniel Mack <daniel-cYrQPVfZoowdnm+yROfE0A@public.gmane.org>,
Haojian Zhuang
<haojian.zhuang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Robert Jarzmik <robert.jarzmik-GANU6spQydw@public.gmane.org>,
"linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] spi: spi-pxa2xx: only include mach/dma.h for legacy DMA
Date: Wed, 4 Feb 2015 06:58:52 -0600 [thread overview]
Message-ID: <CAL_JsqLWVk_QA4ag61S3CTr-RhqcNs-kf=bs+MAsmaRjCCUyTA@mail.gmail.com> (raw)
In-Reply-To: <20150204103027.GS21293-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
On Wed, Feb 4, 2015 at 4:30 AM, Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> wrote:
> On Tue, Feb 03, 2015 at 05:03:35PM -0600, Rob Herring wrote:
>
>> Move the include of mach/dma.h to the legacy PXA DMA code where it is used.
>> This enables building spi-pxa2xx on ARM64.
>
> If this enables the building of spi-pxa2xx on ARMv8 I'd expect to see a
> Kconfig change as well, we're not getting build failures at the minute?
Sorry, I should have said it is in preparation to enable/add ARCH_MMP
on ARM64 for PXA1928.
Rob
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-02-04 12:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-03 23:03 [PATCH] spi: spi-pxa2xx: only include mach/dma.h for legacy DMA Rob Herring
[not found] ` <1423004615-16085-1-git-send-email-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2015-02-04 10:30 ` Mark Brown
[not found] ` <20150204103027.GS21293-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-02-04 12:58 ` Rob Herring [this message]
2015-02-04 20:14 ` Mark Brown
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='CAL_JsqLWVk_QA4ag61S3CTr-RhqcNs-kf=bs+MAsmaRjCCUyTA@mail.gmail.com' \
--to=robh-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=daniel-cYrQPVfZoowdnm+yROfE0A@public.gmane.org \
--cc=haojian.zhuang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=robert.jarzmik-GANU6spQydw@public.gmane.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;
as well as URLs for NNTP newsgroup(s).