From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Baruch Siach <baruch-NswTu9S1W3P6gbPvEgmw2w@public.gmane.org>
Cc: linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v3 2/3] Doc: spi: document the transfer_one spi_master callback
Date: Mon, 27 Jan 2014 18:44:47 +0000 [thread overview]
Message-ID: <20140127184447.GH11841@sirena.org.uk> (raw)
In-Reply-To: <22346e0270dfd9b7892ff313654a6a2001654ea2.1390681463.git.baruch-NswTu9S1W3P6gbPvEgmw2w@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 159 bytes --]
On Sat, Jan 25, 2014 at 10:36:14PM +0200, Baruch Siach wrote:
> Signed-off-by: Baruch Siach <baruch-NswTu9S1W3P6gbPvEgmw2w@public.gmane.org>
Applied, thanks.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-01-27 18:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-25 20:36 [PATCH v3 0/3] spi: documentation improvements Baruch Siach
[not found] ` <cover.1390681463.git.baruch-NswTu9S1W3P6gbPvEgmw2w@public.gmane.org>
2014-01-25 20:36 ` [PATCH v3 1/3] spi: spi.h: clarify the documentation of transfer_one Baruch Siach
[not found] ` <598dd86dc07d794d7cd19a3259ea71618ba150bd.1390681463.git.baruch-NswTu9S1W3P6gbPvEgmw2w@public.gmane.org>
2014-01-27 18:44 ` Mark Brown
2014-01-25 20:36 ` [PATCH v3 2/3] Doc: spi: document the transfer_one spi_master callback Baruch Siach
[not found] ` <22346e0270dfd9b7892ff313654a6a2001654ea2.1390681463.git.baruch-NswTu9S1W3P6gbPvEgmw2w@public.gmane.org>
2014-01-27 18:44 ` Mark Brown [this message]
2014-01-25 20:36 ` [PATCH v3 3/3] spi: correct the transfer_one_message documentation wording Baruch Siach
[not found] ` <c3cea38bd5e725eda84a72e5c9af9d0e66b48a5c.1390681463.git.baruch-NswTu9S1W3P6gbPvEgmw2w@public.gmane.org>
2014-01-27 18:45 ` 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=20140127184447.GH11841@sirena.org.uk \
--to=broonie-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=baruch-NswTu9S1W3P6gbPvEgmw2w@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).