public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/4] ARM: mvebu: fix NOR bus-width in Armada XP GP Device Tree
Date: Thu, 17 Apr 2014 09:09:36 +0200	[thread overview]
Message-ID: <20140417090936.387c79c6@skate> (raw)
In-Reply-To: <20140417050832.GP28159@titan.lakedaemon.net>

Dear Jason Cooper,

On Thu, 17 Apr 2014 01:08:32 -0400, Jason Cooper wrote:

> Patches 2, 3, and 4 applied to mvebu/dt-fixes for stable with Gregory
> and Ezequiel's Acks.

Thanks.

> Also, a gentle nit:  You're doing all the -stable info digging, would
> you mind putting it in the following format so I don't have to hand edit
> each patch?

Sure! So far I've just been blindly following
Documentation/stable_kernel_rules.txt, and besides the "Cc:
stable at vger.kernel.org" it doesn't say anything else of what you're
suggesting below.

> ------
> Link: ...

What should this link point to?

> Fixes: da8d1b383568 ('ARM: mvebu: Add support for NOR flash device on Armada XP-GP board')

Ok. But this is not described in Documentation/stable_kernel_rules.txt.

> Cc: stable at vger.kernel.org # v3.10+

The Cc: to stable@ is documented, but the use of a comment with the
kernel version afterwards is only mentioned when the commit in question
requires other commits as dependencies to be applied to stable. When
the commit is self-sufficient, stable_kernel_rules.txt doesn't indicate
that a comment is needed.

Maybe an update to stable_kernel_rules.txt is in order? :-)

Thanks again!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-04-17  7:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-14 15:29 [PATCH v2 0/4] ARM: mvebu: fix bus width handling in mvebu-devbus Thomas Petazzoni
2014-04-14 15:29 ` [PATCH v2 1/4] memory: mvebu-devbus: fix the conversion of the bus width Thomas Petazzoni
2014-04-16 21:09   ` Jason Cooper
2014-04-16 21:28     ` Thomas Petazzoni
2014-04-17  4:48   ` Jason Cooper
2014-04-14 15:29 ` [PATCH v2 2/4] ARM: mvebu: fix NOR bus-width in Armada XP GP Device Tree Thomas Petazzoni
2014-04-17  5:08   ` Jason Cooper
2014-04-17  7:09     ` Thomas Petazzoni [this message]
2014-04-17 14:23       ` Jason Cooper
2014-04-14 15:29 ` [PATCH v2 3/4] ARM: mvebu: fix NOR bus-width in Armada XP DB " Thomas Petazzoni
2014-04-14 15:29 ` [PATCH v2 4/4] ARM: mvebu: fix NOR bus-width in Armada XP OpenBlocks AX3 " Thomas Petazzoni
2014-04-14 17:00 ` [PATCH v2 0/4] ARM: mvebu: fix bus width handling in mvebu-devbus Ezequiel Garcia
2014-04-16  8:17 ` 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=20140417090936.387c79c6@skate \
    --to=thomas.petazzoni@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