From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] spi: orion: Fix maximum baud rates for Armada 370/XP
Date: Tue, 26 May 2015 14:08:43 +0200 [thread overview]
Message-ID: <5564624B.1030503@free-electrons.com> (raw)
In-Reply-To: <20150526103650.GM21577@sirena.org.uk>
Hi Mark,
On 26/05/2015 12:36, Mark Brown wrote:
> On Tue, May 26, 2015 at 11:44:42AM +0200, Gregory CLEMENT wrote:
>
>> Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
>> Reported-by: Kostya Porotchkin <kostap@marvell.com>
>> Cc: <stable@vger.kernel.org> #Fixes df59fa7f4bca
>
> Applied, but please format this stuff in a standard fashion - use a
> Fixes: tag to reference commits you're fixing. This makes it easier for
> tooling to work with the information you're providing.
Yes, sure, I will do. I followed the Documentation/stable_kernel_rules.txt
file and I missed the new information in Documentation/SubmittingPatches
about this tag.
Thanks,
Gregory
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2015-05-26 12:08 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 [this message]
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
2015-05-27 17:45 ` Mark Brown
2015-05-27 17:47 ` Gregory CLEMENT
2015-05-27 18:39 ` Mark Brown
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=5564624B.1030503@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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).