From: Linus Torvalds <torvalds@linux-foundation.org>
To: Will Deacon <will.deacon@arm.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] arm64: Second round of fixes for -rc2
Date: Tue, 20 Aug 2019 11:18:11 -0700 [thread overview]
Message-ID: <CAHk-=whxG=phQsXxfmeS83MEsks55faRODxxrxfCzdiEideGqg@mail.gmail.com> (raw)
In-Reply-To: <20190820093709.GD14085@fuggles.cambridge.arm.com>
On Tue, Aug 20, 2019 at 2:37 AM Will Deacon <will.deacon@arm.com> wrote:
>
> Thanks to the tech comms folks at Arm, this should now be available and
> work is ongoing to open up more of the documentation too.
Thanks.
> For example, the A76 SDEN is here:
>
> https://static.docs.arm.com/sden885749/d/Arm_Cortex-A76_MP052_Software_Developer_Errata_Notice_v16.0.pdf
>
> and if you hammer "cortex a76 1463225" into google, then it shows up
> after the Linux hits.
Yeah, I have long since given up on trying to keep track of everything
going on, which is why "google finds it" is important to me. And I
verified that yes, now google finds the ARM errata ;)
Lovely,
Linus
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-08-20 18:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 17:43 [GIT PULL] arm64: Second round of fixes for -rc2 Will Deacon
2019-05-24 18:14 ` Linus Torvalds
2019-05-24 18:19 ` Will Deacon
2019-08-20 9:37 ` Will Deacon
2019-08-20 18:18 ` Linus Torvalds [this message]
2019-05-24 18:20 ` pr-tracker-bot
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='CAHk-=whxG=phQsXxfmeS83MEsks55faRODxxrxfCzdiEideGqg@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=will.deacon@arm.com \
/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).