All of lore.kernel.org
 help / color / mirror / Atom feed
From: shinya.kuribayashi.px@renesas.com (Shinya Kuribayashi)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM errata corrections
Date: Tue, 20 Dec 2011 17:36:51 +0900	[thread overview]
Message-ID: <4EF04923.50203@renesas.com> (raw)

Hello Catalin, Will (and Dave, may be interested in),

I've been holding these two patches at hand for more than a year, but
don't want to any further.  This kind of errata updates can be easily
overlooked, or even if proper patches are prepared, it is so easy to
forget to up-port them when upgrading the kernels.

I believe we have many r2pX Cortex-A9 MPcore silicons out there.  Let's
get them corrected in the master.

Could you take a look please?
-- 
Shinya Kuribayashi
Renesas Electronics

             reply	other threads:[~2011-12-20  8:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-20  8:36 Shinya Kuribayashi [this message]
2011-12-20  8:37 ` [PATCH] ARM: errata: Update the workaround for the 742231 Cortex-A9 erratum Shinya Kuribayashi
2011-12-20 14:15   ` Catalin Marinas
2011-12-20  8:38 ` [PATCH] ARM: errata: Faulty logic in the Store Buffer may lead to data corruption Shinya Kuribayashi
2011-12-20 10:26   ` Catalin Marinas

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=4EF04923.50203@renesas.com \
    --to=shinya.kuribayashi.px@renesas.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.