linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: <stable@vger.kernel.org>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: stable: Please include commit bb344ca5b90 ("powerpc/mpc85xx: Add ranges to etsec2 nodes")
Date: Thu, 26 Mar 2015 16:14:27 -0500	[thread overview]
Message-ID: <20150326211427.GA20872@home.buserror.net> (raw)

Commit bb344ca5b90df6 ("powerpc/mpc85xx: Add ranges to etsec2 nodes")
fixes a bug that was exposed by commit 746c9e9f92dd ("of/base: Fix
PowerPC address parsing hack").  The latter commit was applied to stable
trees, so the former should be as well.

-Scott

             reply	other threads:[~2015-03-26 21:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-26 21:14 Scott Wood [this message]
2015-03-30 10:20 ` stable: Please include commit bb344ca5b90 ("powerpc/mpc85xx: Add ranges to etsec2 nodes") Luis Henriques
2015-03-31  9:33 ` Jiri Slaby
2015-06-15  3:32 ` Zefan Li

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=20150326211427.GA20872@home.buserror.net \
    --to=scottwood@freescale.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=stable@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;
as well as URLs for NNTP newsgroup(s).