From: davem@davemloft.net (David Miller)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH net RESEND] PCI: fix oops when try to find Root Port for a PCI device
Date: Wed, 16 Aug 2017 13:59:52 -0700 (PDT) [thread overview]
Message-ID: <20170816.135952.1915098012719012810.davem@davemloft.net> (raw)
In-Reply-To: <20170816200237.GE28977@bhelgaas-glaptop.roam.corp.google.com>
From: Bjorn Helgaas <helgaas@kernel.org>
Date: Wed, 16 Aug 2017 15:02:37 -0500
> Your fix looks right to me.
Someone please submit this fix formally because this change is now in
Linus's tree.
Thank you.
next prev parent reply other threads:[~2017-08-16 20:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 15:24 [PATCH net RESEND] PCI: fix oops when try to find Root Port for a PCI device Ding Tianhong
2017-08-15 17:03 ` Bjorn Helgaas
2017-08-16 0:26 ` David Miller
2017-08-16 19:33 ` Thierry Reding
2017-08-16 20:02 ` Bjorn Helgaas
2017-08-16 20:59 ` David Miller [this message]
2017-08-17 1:14 ` Ding Tianhong
2017-08-17 5:12 ` Michael Ellerman
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=20170816.135952.1915098012719012810.davem@davemloft.net \
--to=davem@davemloft.net \
--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).