From: <jiada_wang@mentor.com>
To: <broonie@kernel.org>
Cc: <linux-spi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Jiada Wang <jiada_wang@mentor.com>
Subject: [PATCH linux-next v2 0/2] follow up fix patch for dynamic burst
Date: Tue, 23 May 2017 07:35:27 -0700 [thread overview]
Message-ID: <1495550129-3489-1-git-send-email-jiada_wang@mentor.com> (raw)
From: Jiada Wang <jiada_wang@mentor.com>
v1:
only allow to use dynamic burst in PIO mode, to address the issue
reported by Fabio
v2:
add one more patch to avoid direct manipulation of tx_buf,
to address the issue reported by Sascha
Jiada Wang (2):
spi: imx: only allow dynamic burst in PIO mode
spi: imx: don't manipulate trasnfer buffer directly
drivers/spi/spi-imx.c | 84 ++++++++++++++++++++++++---------------------------
1 file changed, 39 insertions(+), 45 deletions(-)
--
2.7.4
next reply other threads:[~2017-05-23 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 14:35 jiada_wang [this message]
2017-05-23 14:35 ` [PATCH linux-next v2 1/2] spi: imx: only allow dynamic burst in PIO mode jiada_wang
2017-05-23 14:35 ` [PATCH linux-next v2 2/2] spi: imx: don't manipulate trasnfer buffer directly jiada_wang
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=1495550129-3489-1-git-send-email-jiada_wang@mentor.com \
--to=jiada_wang@mentor.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@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;
as well as URLs for NNTP newsgroup(s).