From: Mark Brown <broonie@kernel.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] SPI: EMMA Mobile SPI master driver
Date: Mon, 16 Sep 2013 23:21:35 +0000 [thread overview]
Message-ID: <20130916232135.GA21013@sirena.org.uk> (raw)
In-Reply-To: <1378386669-9920-2-git-send-email-ian.molton@codethink.co.uk>
[-- Attachment #1: Type: text/plain, Size: 269 bytes --]
On Fri, Sep 06, 2013 at 11:16:14AM +0900, Simon Horman wrote:
> I suspect that Magnus is the best person to review this code
> (although he may have other ideas). Nonetheless, I have made
> a few comments below.
You also need to send it to the SPI maintainer (me)...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-09-16 23:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 13:11 [PATCH] SPI: EMMA Mobile SPI master driver Ian Molton
2013-09-06 2:16 ` Simon Horman
2013-09-16 23:21 ` Mark Brown [this message]
2013-09-17 13:23 ` Mark Brown
2013-09-17 14:30 ` Ian Molton
2013-09-17 16:41 ` 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=20130916232135.GA21013@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-sh@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).