linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: James Puthukattukaran <james.puthukattukaran@oracle.com>
Cc: Sinan Kaya <okaya@codeaurora.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH 0/2] PCI: Support to workaround bus level HW issues
Date: Thu, 19 Apr 2018 12:08:03 -0600	[thread overview]
Message-ID: <20180419120803.3d5791b4@w520.home> (raw)
In-Reply-To: <b6439e86-2284-5b3c-3656-a0c3c2568317@oracle.com>

On Thu, 19 Apr 2018 13:36:00 -0400
James Puthukattukaran <james.puthukattukaran@oracle.com> wrote:

> There are bugs in certain PCIe switches that cause access violations
>  when an endpoint device is hotplugged. In particular, there's an issue
> with
> certain IDT switches that trigger a ACS violation when bringing up a newly
> plugged PCIe endpoint device. This is a major issue for platforms
> designed to
> issue a fatal reset in the case of this event.
> 
> The first patch provides a framework for intercepting and working around
> issues with parent devices to the endpoint being brought up.
> 
> The second patch provides the actual patch for the IDT switch issue using
> that framework. The ACS feature is disabled in the IDT switch prior to
> endpoint
> device detection and then re-enabled subsequent to that.

I'm happy with the logic of the patch, but:

 - Patches are lined wrapped
 - There are white space issues (space indenting and extra returns)
 - 'return(foo(bar));' has too many parens, using 'return foo(bar);'
 - Comment style, see Documentation/process/coding-style.rst for
   preferred multi-line inline comment style.  (I see mixed comment
   style in quirks.c, but probe.c is pretty consistent)
 - Please don't fixup style issues in patch 1/2 in patch 2/2

scripts/checkpatch.pl can find some of these for you.  Thanks,

Alex

  parent reply	other threads:[~2018-04-19 18:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-19 17:36 [PATCH 0/2] PCI: Support to workaround bus level HW issues James Puthukattukaran
2018-04-19 17:37 ` [PATCH 1/2] PCI: Add pci_bus_specific_read_dev_vendor_id() to workaround PCI switch specific issues prior to accessing newly added endpoint James Puthukattukaran
2018-04-19 17:39 ` [PATCH 2/2] PCI: Implement workaround for the ACS bug in the IDT, switch James Puthukattukaran
2018-04-19 18:08 ` Alex Williamson [this message]
2018-04-24 14:57   ` [PATCH 0/2] PCI: Support to workaround bus level HW issues James Puthukattukaran
  -- strict thread matches above, loose matches on Subject: below --
2018-04-24 14:51 [PATCH 0/2] PCI: SUpport " James Puthukattukaran

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=20180419120803.3d5791b4@w520.home \
    --to=alex.williamson@redhat.com \
    --cc=james.puthukattukaran@oracle.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=okaya@codeaurora.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).