linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP2: Enable Errata 430973 for OMAP3
Date: Thu, 9 Jun 2016 01:03:38 -0700	[thread overview]
Message-ID: <20160609080337.GO22406@atomide.com> (raw)
In-Reply-To: <20160609075734.GA8595@earth>

* Sebastian Reichel <sre@kernel.org> [160609 01:00]:
> Hi,
> 
> On Thu, Jun 09, 2016 at 12:15:13AM -0700, Tony Lindgren wrote:
> > * Nishanth Menon <nm@ti.com> [160519 16:23]:
> > > Enable Erratum 430973 similar to commit 5c86c5339c56 ("ARM:
> > > omap2plus_defconfig: Enable ARM erratum 430973 for omap3") - Since
> > > multiple defconfigs can exist from various points of view (multi_v7,
> > > omap2plus etc.. it is always better to enable the erratum from the
> > > Kconfig selection point of view so that downstream kernels dont have
> > > to rediscover this all over again.
> > 
> > This should safe to select now. Note that proc-v7.S still does not
> > do anything with multiarch to configure it. So the bootloader still
> > needs to enable it, or it needs to be done in the machine init like
> > n900 does.
> 
> mh I totally forgot about 430973. I still think [0] is the
> better solution. IIRC I never uploaded them to Russel's
> patchsystem, though :(
> 
> [0] http://comments.gmane.org/gmane.linux.kernel/2002603

Sure makes sense to me. Meanwhile, Nishanth's patch prevents
hitting the same issue over and over.

Regards,

Tony

      reply	other threads:[~2016-06-09  8:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-19 23:20 [PATCH] ARM: OMAP2: Enable Errata 430973 for OMAP3 Nishanth Menon
2016-06-09  7:15 ` Tony Lindgren
2016-06-09  7:57   ` Sebastian Reichel
2016-06-09  8:03     ` Tony Lindgren [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=20160609080337.GO22406@atomide.com \
    --to=tony@atomide.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).