public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Gregory CLEMENT <gregory.clement@free-electrons.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
	linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jason Cooper <jason@lakedaemon.net>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
	linux-arm-kernel@lists.infradead.org,
	Maxime Ripard <maxime.ripard@free-electrons.com>,
	Boris BREZILLON <boris.brezillon@free-electrons.com>,
	Lior Amsalem <alior@marvell.com>,
	Tawfik Bayouk <tawfik@marvell.com>,
	Nadav Haklai <nadavh@marvell.com>,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 2/3] spi: orion: Fix extended baud rates for each Armada SoCs
Date: Wed, 27 May 2015 19:39:08 +0100	[thread overview]
Message-ID: <20150527183908.GN21577@sirena.org.uk> (raw)
In-Reply-To: <55660343.9060200@free-electrons.com>

[-- Attachment #1: Type: text/plain, Size: 434 bytes --]

On Wed, May 27, 2015 at 07:47:47PM +0200, Gregory CLEMENT wrote:
> On 27/05/2015 19:45, Mark Brown wrote:

> > I fixed it up locally (in general it's easier to just send the patch
> > though).

> Thanks! And next time I will send a v2 then if it is easier for you.

I'd say it's just easier in general - "can you please either fix this up
locally or apply this patch" means that whatever the answer is it can be
acted on immediately.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2015-05-27 18:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-26  9:44 [PATCH 0/3] Fix baud rate for Armada SoCs Gregory CLEMENT
2015-05-26  9:44 ` [PATCH 1/3] spi: orion: Fix maximum baud rates for Armada 370/XP Gregory CLEMENT
2015-05-26 10:36   ` Mark Brown
2015-05-26 12:08     ` Gregory CLEMENT
2015-05-26  9:44 ` [PATCH 2/3] spi: orion: Fix extended baud rates for each Armada SoCs Gregory CLEMENT
2015-05-26 10:38   ` Mark Brown
2015-05-26 12:08   ` Andrew Lunn
2015-05-26 12:20     ` Gregory CLEMENT
     [not found]       ` <556464F8.1020707-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2015-05-27 17:45         ` Mark Brown
     [not found]           ` <20150527174547.GI21577-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-05-27 17:47             ` Gregory CLEMENT
2015-05-27 18:39               ` Mark Brown [this message]
2015-05-26  9:44 ` [PATCH 3/3] ARM: mvebu: use improved armada spi device tree compatible name for each SoC Gregory CLEMENT
2015-05-27 10:04   ` Gregory CLEMENT

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=20150527183908.GN21577@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alior@marvell.com \
    --cc=andrew@lunn.ch \
    --cc=boris.brezillon@free-electrons.com \
    --cc=devicetree@vger.kernel.org \
    --cc=ezequiel.garcia@free-electrons.com \
    --cc=gregory.clement@free-electrons.com \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=maxime.ripard@free-electrons.com \
    --cc=nadavh@marvell.com \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=tawfik@marvell.com \
    --cc=thomas.petazzoni@free-electrons.com \
    /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