From: Bjorn Helgaas <helgaas@kernel.org>
To: Shlomo Pongratz <shlomopongratz@gmail.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
andrew.maier@eideticom.com, logang@deltatee.com,
bhelgaas@google.com, jgg@nvidia.com,
Shlomo Pongratz <shlomop@pliops.com>
Subject: Re: [PATCH V5 1/1] Intel Sky Lake-E host root ports check.
Date: Thu, 31 Mar 2022 09:31:01 -0500 [thread overview]
Message-ID: <20220331143101.GA4846@bhelgaas> (raw)
In-Reply-To: <20220331073539.14499-2-shlomop@pliops.com>
On Thu, Mar 31, 2022 at 10:35:39AM +0300, Shlomo Pongratz wrote:
> In commit 7b94b53db34f ("PCI/P2PDMA: Add Intel Sky Lake-E Root Ports B, C, D to
> the whitelist")
> Andrew Maier added the Sky Lake-E additional devices
> 2031, 2032 and 2033 root ports to the already existing 2030 device.
>
> The Intel devices 2030, 2031, 2032 and 2033 which are root ports A, B, C and D,
> respectively and if all exist they will occupy slots 0 till 3 in that order.
Please make this a sentence.
> The original code handled only the case where the devices in the whitelist are
> host bridges and assumed that they will be found on slot 0.
>
> This assumption doesn't hold for root ports so an explicit test was added to
> cover this case.
Please update the subject line to match the style of previous ones.
Please wrap the commit log to fit in 80 columns (including the 4
spaces added by "git log") like previous commits.
Please figure out whether you want "Sky Lake-E" or "SkyLake-E" and use
it consistently in commit log and code comments. It seems to be
"Skylake" on intel.com, so I suggest using that.
Please use imperative mood, e.g., instead of "an explicit test was
added ...," write "add a test to cover this case." Do the same in
code comments.
Bjorn
next prev parent reply other threads:[~2022-03-31 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 7:35 [PATCH V5 0/1] Intel Sky Lake-E host root ports check Shlomo Pongratz
2022-03-31 7:35 ` [PATCH V5 1/1] " Shlomo Pongratz
2022-03-31 14:31 ` Bjorn Helgaas [this message]
2022-04-01 16:11 ` Shlomo Pongratz
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=20220331143101.GA4846@bhelgaas \
--to=helgaas@kernel.org \
--cc=andrew.maier@eideticom.com \
--cc=bhelgaas@google.com \
--cc=jgg@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=shlomop@pliops.com \
--cc=shlomopongratz@gmail.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