SUPERH platform development
 help / color / mirror / Atom feed
From: Luis Henriques <luis.henriques@canonical.com>
To: linux-sh@vger.kernel.org
Subject: Re: [3.16.y-ckt stable] Patch "ARM: shmobile: r8a7791: Correct SDHI clock labels and output-names" h
Date: Wed, 06 May 2015 10:35:25 +0000	[thread overview]
Message-ID: <20150506103525.GB1691@ares.olymp> (raw)
In-Reply-To: <CAMuHMdUcXZZdof-OOowWJ9wuwQeD9Hu5qOp=CKvVO0KttbAdsw@mail.gmail.com>

On Wed, May 06, 2015 at 12:28:34PM +0200, Geert Uytterhoeven wrote:
> Hi Luis,
> 
> On Wed, May 6, 2015 at 11:52 AM, Luis Henriques
> <luis.henriques@canonical.com> wrote:
> > This is a note to let you know that I have just added a patch titled
> >
> >     ARM: shmobile: r8a7791: Correct SDHI clock labels and output-names
> >
> > to the linux-3.16.y-queue branch of the 3.16.y-ckt extended stable tree
> > which can be found at:
> >
> >     http://kernel.ubuntu.com/git/ubuntu/linux.git/log/?h=linux-3.16.y-queue
> >
> > This patch is scheduled to be released in version 3.16.7-ckt11.
> >
> > If you, or anyone else, feels it should not be added to this tree, please
> > reply to this email.
> 
> Unless you want to queue other patches that depend on this, I don't think
> there's a need to backport this to -stable:
>   - Changing the names of the labels doesn't have any visible effects,
>     as the phandles referring to them are changed, too,
>   - IIRC, nothing relies on the (changed) names of qclock-output-names.
>

Ok, that makes sense to me -- patch dropped from the 3.16 queue.
Thank you for you review.

Cheers,
--
Luís

      reply	other threads:[~2015-05-06 10:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-06 10:28 [3.16.y-ckt stable] Patch "ARM: shmobile: r8a7791: Correct SDHI clock labels and output-names" h Geert Uytterhoeven
2015-05-06 10:35 ` Luis Henriques [this message]

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=20150506103525.GB1691@ares.olymp \
    --to=luis.henriques@canonical.com \
    --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