From: David Miller <davem@davemloft.net>
To: bhelgaas@google.com
Cc: wangyijing@huawei.com, linux-pci@vger.kernel.org, mroos@linux.ee,
sparclinux@vger.kernel.org, eric.snowberg@oracle.com,
benh@kernel.crashing.org
Subject: Re: [PATCH] PCI/ASPM: Fix a NULL pointer crash on sparc64
Date: Thu, 20 Aug 2015 14:38:15 -0700 (PDT) [thread overview]
Message-ID: <20150820.143815.1802014224351735588.davem@davemloft.net> (raw)
In-Reply-To: <20150820212109.GB14810@google.com>
From: Bjorn Helgaas <bhelgaas@google.com>
Date: Thu, 20 Aug 2015 16:21:09 -0500
> On Thu, Aug 20, 2015 at 01:58:32PM -0700, David Miller wrote:
>> From: Bjorn Helgaas <bhelgaas@google.com>
>> Date: Thu, 20 Aug 2015 15:21:35 -0500
>>
>> > On Thu, Aug 20, 2015 at 11:40:42AM -0700, David Miller wrote:
>> >> From: Bjorn Helgaas <bhelgaas@google.com>
>> >> Date: Thu, 20 Aug 2015 11:23:43 -0700
>> >>
>> >> > On Thu, Aug 20, 2015 at 10:47 AM, David Miller <davem@davemloft.net> wrote:
>> >> >> From: Bjorn Helgaas <bhelgaas@google.com>
>> >> >> Date: Thu, 20 Aug 2015 00:48:00 -0500
>> >> >>
>> >> >>> [+cc Dave, Eric, Ben, sparclinux]
>> >> >>
>> >> >> I think the comment is terrible.
>> >> >
>> >> > I'll update the comment if you suggest some text. Do you object
>> >> > mainly to the mention of the specific systems?
>> >>
>> >> "PCI root complex can not be assumed to be instantiated in the PCI bus
>> >> hierarchy."
>> >
>> > AIUI, the root complex itself (as distinct from root ports) doesn't
>> > normally appear in the PCI hierarchy, so I reworded it as follows. I hope
>> > this helps address your objection, but if not, I can try again.
>>
>> This is fine, but it was the comment we were talking about adjusting not
>> the commit message :-)
>
> Oh, sorry! I totally misread that. Here's another try.
This also looks fine:
Acked-by: David S. Miller <davem@davemloft.net>
next prev parent reply other threads:[~2015-08-20 21:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 10:47 [PATCH] PCI/ASPM: Fix a NULL pointer crash on sparc64 Yijing Wang
2015-08-18 18:49 ` Bjorn Helgaas
2015-08-18 19:10 ` David Miller
2015-08-19 22:16 ` Bjorn Helgaas
2015-08-19 22:29 ` Benjamin Herrenschmidt
2015-08-20 6:01 ` Bjorn Helgaas
2015-08-20 6:38 ` Benjamin Herrenschmidt
2015-08-20 6:44 ` Kjetil Oftedal
2015-08-20 17:51 ` David Miller
2015-08-20 17:50 ` David Miller
2015-08-20 5:48 ` Bjorn Helgaas
2015-08-20 17:47 ` David Miller
2015-08-20 18:23 ` Bjorn Helgaas
2015-08-20 18:40 ` David Miller
2015-08-20 20:21 ` Bjorn Helgaas
2015-08-20 20:58 ` David Miller
2015-08-20 21:21 ` Bjorn Helgaas
2015-08-20 21:38 ` David Miller [this message]
2015-08-21 1:48 ` wangyijing
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=20150820.143815.1802014224351735588.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=eric.snowberg@oracle.com \
--cc=linux-pci@vger.kernel.org \
--cc=mroos@linux.ee \
--cc=sparclinux@vger.kernel.org \
--cc=wangyijing@huawei.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).