linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: drop ISAR0 workaround for B15
Date: Wed, 3 Sep 2014 10:03:01 +0100	[thread overview]
Message-ID: <20140903090301.GA32378@arm.com> (raw)
In-Reply-To: <20140902234924.GZ18411@ld-irv-0074>

On Wed, Sep 03, 2014 at 12:49:24AM +0100, Brian Norris wrote:
> Ping.
> 
> Is this worthy of 3.17-rc? Or should it just be queued for 3.18, as it's
> only removing redundant info?

Since it's not actually fixing anything, I don't think it qualifies as a
fix. You can still put it into rmk's patch system though, as I don't see
this conflicting with anything in the pipeline.

Will

      reply	other threads:[~2014-09-03  9:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-11 22:44 [PATCH] ARM: Explain workaround for faulty ISAR0 register on B15 Gregory Fong
2014-08-13 18:53 ` Gregory Fong
2014-08-13 19:40 ` [PATCH] ARM: drop ISAR0 workaround for B15 Brian Norris
2014-09-02 23:49   ` Brian Norris
2014-09-03  9:03     ` Will Deacon [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=20140903090301.GA32378@arm.com \
    --to=will.deacon@arm.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).