From: Sekhar Nori <nsekhar-l0cyMroinI0@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Grygorii Strashko
<grygorii.strashko-l0cyMroinI0@public.gmane.org>,
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linux ARM Mailing List
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
<linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: [PATCH v2 0/2] spi: davinci: fix spurious i/o error
Date: Thu, 10 Dec 2015 21:59:03 +0530 [thread overview]
Message-ID: <cover.1449764266.git.nsekhar@ti.com> (raw)
This patch series fixes a spurious I/O error with
DaVinci SPI.
v2:
- Update to handle DMA case
- add a patch to use dev_err() for error reporting
Sekhar Nori (2):
spi: davinci: fix spurious i/o error
spi: davinci: use dev_err() for error reporting
drivers/spi/spi-davinci.c | 17 +++++++++--------
1 file changed, 9 insertions(+), 8 deletions(-)
--
2.6.3
--
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 reply other threads:[~2015-12-10 16:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 16:29 Sekhar Nori [this message]
2015-12-10 16:29 ` [PATCH v2 1/2] spi: davinci: fix spurious i/o error Sekhar Nori
[not found] ` <fbcc972e6612cf3d069e7230dd078d8a1e0e2e5a.1449764266.git.nsekhar-l0cyMroinI0@public.gmane.org>
2015-12-12 23:08 ` Applied "spi: davinci: fix spurious i/o error" to the spi tree Mark Brown
2015-12-10 16:29 ` [PATCH v2 2/2] spi: davinci: use dev_err() for error reporting Sekhar Nori
[not found] ` <83b3c0bb63ff958d10c773ab7bf128393cc7ddad.1449764266.git.nsekhar-l0cyMroinI0@public.gmane.org>
2015-12-12 23:08 ` Applied "spi: davinci: use dev_err() for error reporting" to the spi tree Mark Brown
[not found] ` <cover.1449764266.git.nsekhar-l0cyMroinI0@public.gmane.org>
2015-12-17 13:26 ` [PATCH v2 0/2] spi: davinci: fix spurious i/o error Grygorii Strashko
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=cover.1449764266.git.nsekhar@ti.com \
--to=nsekhar-l0cymroini0@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=grygorii.strashko-l0cyMroinI0@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@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).