From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: <linux-pci@vger.kernel.org>, Bjorn Helgaas <helgaas@kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/8] PCI/treewide: PCIe Link Width field access cleanup
Date: Tue, 12 Sep 2023 11:24:53 +0100 [thread overview]
Message-ID: <20230912112453.000015f6@Huawei.com> (raw)
In-Reply-To: <20230911121501.21910-1-ilpo.jarvinen@linux.intel.com>
On Mon, 11 Sep 2023 15:14:53 +0300
Ilpo Järvinen <ilpo.jarvinen@linux.intel.com> wrote:
> Instead of custom code to extract the PCIe Negotiated and Maximum Link
> Width fields, make the code more obvious using FIELD_GET/PREP().
>
> Ilpo Järvinen (8):
> IB/hfi1: Use FIELD_GET() to extract Link Width
> media: cobalt: Use FIELD_GET() to extract Link Width
> igb: Use FIELD_GET() to extract Link Width
> PCI: tegra194: Use FIELD_GET()/FIELD_PREP() with Link Width fields
> PCI: mvebu: Use FIELD_PREP() with Link Width
> PCI: Use FIELD_GET() to extract Link Width
> scsi: esas2r: Use FIELD_GET() to extract Link Width
> scsi: qla2xxx: Use FIELD_GET() to extract Link Width
I'd like to see this done more generally rather than just
for this one field, but I guess it's a step in the right direction.
I'm particularly in favour of the cases where 4 was used
rather than the define.
>
> drivers/infiniband/hw/hfi1/pcie.c | 5 +++--
As an example, immediately above the link width code is link
speed code. Using FIELD_GET there as well would avoid people
having to 'know' that field is at 0 shift.
So for what you have
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
but I'd like to see this taken further.
A few minor comments in some of the individual patches.
> drivers/media/pci/cobalt/cobalt-driver.c | 11 ++++++-----
> drivers/net/ethernet/intel/igb/e1000_mac.c | 6 +++---
> drivers/pci/controller/dwc/pcie-tegra194.c | 9 ++++-----
> drivers/pci/controller/pci-mvebu.c | 2 +-
> drivers/pci/pci-sysfs.c | 5 ++---
> drivers/pci/pci.c | 6 +++---
> drivers/scsi/esas2r/esas2r_ioctl.c | 8 ++++----
> drivers/scsi/qla2xxx/qla_os.c | 3 ++-
> 9 files changed, 28 insertions(+), 27 deletions(-)
>
prev parent reply other threads:[~2023-09-12 10:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 12:14 [PATCH 0/8] PCI/treewide: PCIe Link Width field access cleanup Ilpo Järvinen
2023-09-11 12:14 ` [PATCH 1/8] IB/hfi1: Use FIELD_GET() to extract Link Width Ilpo Järvinen
2023-09-12 10:26 ` Jonathan Cameron
2023-09-11 12:14 ` [PATCH 2/8] media: cobalt: " Ilpo Järvinen
2023-09-11 12:14 ` [Intel-wired-lan] [PATCH 3/8] igb: " Ilpo Järvinen
2023-09-11 12:14 ` Ilpo Järvinen
2023-09-12 10:34 ` [Intel-wired-lan] " Jonathan Cameron
2023-09-12 10:34 ` Jonathan Cameron
2023-09-12 12:11 ` [Intel-wired-lan] " Ilpo Järvinen
2023-09-12 12:11 ` Ilpo Järvinen
2023-09-11 12:14 ` [PATCH 4/8] PCI: tegra194: Use FIELD_GET()/FIELD_PREP() with Link Width fields Ilpo Järvinen
2023-09-12 10:35 ` Jonathan Cameron
2023-09-11 12:14 ` [PATCH 5/8] PCI: mvebu: Use FIELD_PREP() with Link Width Ilpo Järvinen
2023-09-11 12:14 ` Ilpo Järvinen
2023-09-11 12:14 ` [PATCH 6/8] PCI: Use FIELD_GET() to extract " Ilpo Järvinen
2023-09-11 12:15 ` [PATCH 7/8] scsi: esas2r: " Ilpo Järvinen
2023-09-12 10:38 ` Jonathan Cameron
2023-09-11 12:15 ` [PATCH 8/8] scsi: qla2xxx: " Ilpo Järvinen
2023-09-12 10:39 ` Jonathan Cameron
2023-09-12 10:24 ` Jonathan Cameron [this message]
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=20230912112453.000015f6@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=helgaas@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.