Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1556840

Re: [PATCH v3 2/5] arm64: Work around Falkor erratum 1003

From Mark Rutland <mark.rutland@arm.com>
Newsgroups linux.kernel
Subject Re: [PATCH v3 2/5] arm64: Work around Falkor erratum 1003
Date 2017-01-11 19:50 +0100
Message-ID <sYw8a-1XP-33@gated-at.bofh.it> (permalink)
References (2 earlier) <sYvvt-1Kq-51@gated-at.bofh.it> <sYvYt-1Uj-3@gated-at.bofh.it> <sYvYt-1Uj-1@gated-at.bofh.it> <sYvYu-1Uj-43@gated-at.bofh.it> <sYw8a-1XP-23@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw

On Wed, Jan 11, 2017 at 12:40:42PM -0600, Timur Tabi wrote:
> On 01/11/2017 12:37 PM, Mark Rutland wrote:
> >The name, as it is, is perfectly descriptive.
> >
> >Let's not sacrifice legibility over a non-issue.
> 
> I don't want to kick a dead horse or anything, but changing it to
> QCOM_FLKR_ERRATUM_1003 would eliminate all the spacing problems
> without sacrificing anything.

The CPU is called "Falkor", not "FLKR", and we're not coming up with an
ACPI table name...

The ARM Ltd. erratum numbers are global to all parts, so we don't
include the part name. Is the 1003 erratum number specific to Falkor?

If it's global, you could use QCOM_ERRATUM_1003 instead.

Otherwise, QCOM_FALKOR_ERRATUM_1003 is preferable.

Thanks,
Mark.

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

[PATCH v3 2/5] arm64: Work around Falkor erratum 1003 Christopher Covington <cov@codeaurora.org> - 2017-01-11 15:50 +0100
  Re: [PATCH v3 2/5] arm64: Work around Falkor erratum 1003 Catalin Marinas <catalin.marinas@arm.com> - 2017-01-11 19:10 +0100
    Re: [PATCH v3 2/5] arm64: Work around Falkor erratum 1003 Marc Zyngier <marc.zyngier@arm.com> - 2017-01-11 19:30 +0100
      Re: [PATCH v3 2/5] arm64: Work around Falkor erratum 1003 Mark Rutland <mark.rutland@arm.com> - 2017-01-11 19:50 +0100
        Re: [PATCH v3 2/5] arm64: Work around Falkor erratum 1003 Catalin Marinas <catalin.marinas@arm.com> - 2017-01-12 16:50 +0100
          Re: [PATCH v3 2/5] arm64: Work around Falkor erratum 1003 Mark Rutland <mark.rutland@arm.com> - 2017-01-12 17:20 +0100
      Re: [PATCH v3 2/5] arm64: Work around Falkor erratum 1003 Catalin Marinas <catalin.marinas@arm.com> - 2017-01-12 17:00 +0100
        Re: [PATCH v3 2/5] arm64: Work around Falkor erratum 1003 Will Deacon <will.deacon@arm.com> - 2017-01-12 17:10 +0100
    Re: [PATCH v3 2/5] arm64: Work around Falkor erratum 1003 Timur Tabi <timur@codeaurora.org> - 2017-01-11 19:40 +0100
      Re: [PATCH v3 2/5] arm64: Work around Falkor erratum 1003 Mark Rutland <mark.rutland@arm.com> - 2017-01-11 19:40 +0100
        Re: [PATCH v3 2/5] arm64: Work around Falkor erratum 1003 Timur Tabi <timur@codeaurora.org> - 2017-01-11 19:50 +0100
          Re: [PATCH v3 2/5] arm64: Work around Falkor erratum 1003 Mark Rutland <mark.rutland@arm.com> - 2017-01-11 19:50 +0100
            Re: [PATCH v3 2/5] arm64: Work around Falkor erratum 1003 Christopher Covington <cov@codeaurora.org> - 2017-01-16 15:30 +0100
          Re: [PATCH v3 2/5] arm64: Work around Falkor erratum 1003 Marc Zyngier <marc.zyngier@arm.com> - 2017-01-11 20:00 +0100
        Re: [PATCH v3 2/5] arm64: Work around Falkor erratum 1003 Catalin Marinas <catalin.marinas@arm.com> - 2017-01-12 11:00 +0100
    Re: [PATCH v3 2/5] arm64: Work around Falkor erratum 1003 Mark Rutland <mark.rutland@arm.com> - 2017-01-11 19:40 +0100

csiph-web