From: 21cnbao@gmail.com (Barry Song)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 8/8] spi: sirf: make DMA transfer mode optional
Date: Sun, 07 Sep 2014 08:55:53 +0800 [thread overview]
Message-ID: <D031CD59.21619%21cnbao@gmail.com> (raw)
In-Reply-To: <20140906135550.GD2601@sirena.org.uk>
On 14-9-6 ??9:55, "Mark Brown" <broonie@kernel.org> wrote:
>On Fri, Sep 05, 2014 at 04:14:17PM +0800, Barry Song wrote:
>
>> i have no strong technical reason for this as the benefit is not
>> always technical. you know....the commit log has provided the reason
>> for this patch.
>> the difficulty for me is maintaining the difference between mainline
>> and local codes, but if we have to maintain two copies, we can.
>
>OK, well I think that's best though it would be better if we were able
>to understand what benefit your customers believe they are seeing here
>and hopefully address it in a better way. Doing this sort of thing with
>Kconfig options is not great, especially when you start trying to build
>kernels that work with more than one board.
my goal is doubling-check this with customers, if there is no problem,
drop this one as it is not a valid technical solution.
-barry
next prev parent reply other threads:[~2014-09-07 0:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 9:02 [PATCH 5/8] spi: sirf: add fifo reset/start for cmd transfer Barry Song
2014-09-02 9:02 ` [PATCH 6/8] spi: sirf: set default spi frequency if it is not set Barry Song
2014-09-04 22:39 ` Mark Brown
2014-09-05 7:57 ` Barry Song
2014-09-02 9:02 ` [PATCH 7/8] spi: sirf: cleanup the indentation of marcos Barry Song
2014-09-04 22:39 ` Mark Brown
2014-09-02 9:02 ` [PATCH 8/8] spi: sirf: make DMA transfer mode optional Barry Song
2014-09-04 22:41 ` Mark Brown
2014-09-05 8:14 ` Barry Song
2014-09-06 13:55 ` Mark Brown
2014-09-07 0:55 ` Barry Song [this message]
2014-09-04 22:37 ` [PATCH 5/8] spi: sirf: add fifo reset/start for cmd transfer 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=D031CD59.21619%21cnbao@gmail.com \
--to=21cnbao@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).