From: Mark Brown <broonie@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Sanchayan Maity <maitysanchayan@gmail.com>,
linux-spi <linux-spi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] spi: SPI_FSL_DSPI should depend on HAS_DMA
Date: Wed, 14 Dec 2016 15:13:00 +0000 [thread overview]
Message-ID: <20161214151300.jrq4qexxcjyfk5sv@sirena.org.uk> (raw)
In-Reply-To: <CAMuHMdU6PGUrmMOKFH9AFwK7j-eyThVaofS0jKN=HiL0WupJEA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 610 bytes --]
On Wed, Dec 14, 2016 at 03:40:43PM +0100, Geert Uytterhoeven wrote:
> On Wed, Dec 14, 2016 at 3:37 PM, Mark Brown <broonie@kernel.org> wrote:
> > On Wed, Dec 14, 2016 at 01:28:05PM +0100, Geert Uytterhoeven wrote:
> > Honestly I think we should just fix the architectures that don't support
> > DMA to provide compile out stubs for DMA, it seems like these
> > dependencies are more trouble than they're worth.
> Will that really help?
> Then people will start adding "depends on HAS_DMA || COMPILE_TEST"
> instead...
No, I'm thinking just arrange things so that we don't need to depend on
HAS_DMA at all.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2016-12-14 15:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 12:28 [PATCH] spi: SPI_FSL_DSPI should depend on HAS_DMA Geert Uytterhoeven
2016-12-14 14:37 ` Mark Brown
[not found] ` <20161214143713.3kl34okpr5vnuyc6-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-12-14 14:40 ` Geert Uytterhoeven
2016-12-14 15:13 ` Mark Brown [this message]
[not found] ` <1481718485-6966-1-git-send-email-geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org>
2016-12-14 18:03 ` Applied "spi: SPI_FSL_DSPI should depend on HAS_DMA" to the spi tree 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=20161214151300.jrq4qexxcjyfk5sv@sirena.org.uk \
--to=broonie@kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=maitysanchayan@gmail.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;
as well as URLs for NNTP newsgroup(s).