mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jon Masters <jcm@jonmasters.org>
To: David Daney <ddaney.cavm@gmail.com>,
	Vadim Lomovtsev <Vadim.Lomovtsev@caviumnetworks.com>
Cc: David.Daney@cavium.com, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	stemerkhanov@CAVIUMNETWORKS.onmicrosoft.com,
	Bjorn Helgaas <helgaas@kernel.org>,
	tn@semihalf.com, bhelgaas@google.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] PCI: ACPI: Fix ThunderX PEM initialization
Date: Tue, 21 Mar 2017 07:38:07 -0400	[thread overview]
Message-ID: <c3392131-9243-24d3-30b4-4d7e84019d6f@jonmasters.org> (raw)
In-Reply-To: <48b93116-cc0f-e59d-8aa3-704052ad6759@gmail.com>

On 03/16/2017 12:25 PM, David Daney wrote:
> On 03/16/2017 07:32 AM, Jon Masters wrote:

>>> Yes, it is now contains "CAVxxx" as _HID for device config object.
>>
>> Which is different from the version that was merged into upstream. That
>> should never have happened. It will never happen again. I have spent some
>> time over the past few days ensuring folks understand that I will not
>> allow a repeat of this to occur the next time around. We will have
>> platforms that are bulletproof and supported by upstream with any
>> errata fixes in a very carefully controlled manner. There will
>> under no circumstances ever be a situation like this again.
> 
> We are still evaluating the merits of registering the values that appeared
> in v4.10, and not changing them.  We should know more in a couple of days.

Thanks David. What was the verdict? (for the public record). If we need to
get a change into upstream, let's get that teed up before 4.12 merge.

And for other folks following along with this thread: I'm not just picking
on Cavium here. I'll be doing the same with *every* ARM server SoC company
as necessary over the coming months. We are going to have militantly
compliant standards adherence in this industry and every ARM server SoC is
going to "just work" with an upstream Linux kernel with an ACPI enabled 
platform. This will be so utterly clean and boring it'll be amazing.

Jon.

  reply	other threads:[~2017-03-21 11:55 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-30 16:25 Vadim Lomovtsev
2017-01-30 17:39 ` David Daney
2017-01-30 21:12 ` Bjorn Helgaas
2017-01-31 10:28   ` Vadim Lomovtsev
2017-01-31 14:25     ` Bjorn Helgaas
2017-01-31 14:57       ` Vadim Lomovtsev
2017-01-31 20:31         ` Bjorn Helgaas
2017-02-01 12:53           ` Vadim Lomovtsev
2017-02-01 15:18             ` Bjorn Helgaas
2017-02-01 15:34               ` Vadim Lomovtsev
2017-03-15 11:14               ` Jon Masters
2017-03-15 11:33                 ` Vadim Lomovtsev
2017-03-16 14:32                   ` Jon Masters
2017-03-16 16:25                     ` David Daney
2017-03-21 11:38                       ` Jon Masters [this message]
2017-03-21 13:47                         ` Bjorn Helgaas
2017-03-21 14:17                           ` Tomasz Nowicki
2017-03-21 14:56                             ` David Daney
2017-03-22 14:28                               ` Jon Masters
2017-03-22 14:48                                 ` Bjorn Helgaas
2017-03-22 16:25                                   ` Jon Masters
2017-03-22 16:34                                     ` Bjorn Helgaas
2017-03-23 22:14                                       ` Bjorn Helgaas
2017-03-23 22:16                                         ` Jon Masters
2017-03-21 17:45                             ` Bjorn Helgaas

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=c3392131-9243-24d3-30b4-4d7e84019d6f@jonmasters.org \
    --to=jcm@jonmasters.org \
    --cc=David.Daney@cavium.com \
    --cc=Vadim.Lomovtsev@caviumnetworks.com \
    --cc=bhelgaas@google.com \
    --cc=ddaney.cavm@gmail.com \
    --cc=helgaas@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=stemerkhanov@CAVIUMNETWORKS.onmicrosoft.com \
    --cc=tn@semihalf.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

all inboxes | Powered by JetHome®