From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Chao Fu <b44548-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org
Subject: Re: [PATCH v2 2/2] spi:dspi:Remove some coding sytle not in standard
Date: Thu, 9 Jan 2014 17:53:21 +0000 [thread overview]
Message-ID: <20140109175321.GL12858@sirena.org.uk> (raw)
In-Reply-To: <1389161655-21856-2-git-send-email-b44548-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 268 bytes --]
On Wed, Jan 08, 2014 at 02:14:15PM +0800, Chao Fu wrote:
> From: Chao Fu <B44548-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
>
> Remove some coding sytle not in standard in former code.
This is OK but depends on your previous patch so can't be applied just
yet.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-01-09 17:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 6:14 [PATCH v2 1/2] spi:fsl-dspi:add support of DSPI IP in big endian Chao Fu
[not found] ` <1389161655-21856-1-git-send-email-b44548-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2014-01-08 6:14 ` [PATCH v2 2/2] spi:dspi:Remove some coding sytle not in standard Chao Fu
[not found] ` <1389161655-21856-2-git-send-email-b44548-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2014-01-09 17:53 ` Mark Brown [this message]
2014-01-09 17:52 ` [PATCH v2 1/2] spi:fsl-dspi:add support of DSPI IP in big endian Mark Brown
[not found] ` <20140109175208.GK12858-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-01-10 8:11 ` Chao Fu
[not found] ` <e9c8019df2cf4d76ae2b77c5d1420050-AZ66ij2kwaYw6E1ICcNxleO6mTEJWrR4XA4E9RH9d+qIuWR1G4zioA@public.gmane.org>
2014-01-10 12:40 ` Mark Brown
[not found] ` <20140110124014.GI29039-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-01-10 12:53 ` Russell King - ARM Linux
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=20140109175321.GL12858@sirena.org.uk \
--to=broonie-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=b44548-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@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).