linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: linux-pci@vger.kernel.org,
	Potnuri Bharat Teja <bharat@chelsio.com>,
	 Andrew Lunn <andrew+netdev@lunn.ch>,
	 "David S. Miller" <davem@davemloft.net>,
	 Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,  Netdev <netdev@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] cxgb3: Replace PCI related literals with defines & correct variable
Date: Wed, 11 Jun 2025 10:22:35 +0300 (EEST)	[thread overview]
Message-ID: <a24d9048-d296-9bd5-aa65-4e630dc34d51@linux.intel.com> (raw)
In-Reply-To: <20250610135338.580aa25b@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 1918 bytes --]

On Tue, 10 Jun 2025, Jakub Kicinski wrote:
> On Tue, 10 Jun 2025 13:32:03 +0300 Ilpo Järvinen wrote:
> > Replace literals 0, 2, 0x1425 with PCI_VENDOR_ID, PCI_DEVICE_ID,
> > PCI_VENDOR_ID_CHELSIO, respectively. Rename devid variable to vendor_id
> > to remove confusion.
> 
> This series is missing a cover letter. An explanation of why you're
> touching this very very old driver is in order, and please comment
> on whether you can test this on real HW, because we don't like

No, I don't have the HW available.

> refactoring of very old code:
> 
> Quoting documentation:
> 
>   Clean-up patches
>   ~~~~~~~~~~~~~~~~
>   
>   Netdev discourages patches which perform simple clean-ups, which are not in
>   the context of other work. For example:
>   
>   * Addressing ``checkpatch.pl`` warnings
>   * Addressing :ref:`Local variable ordering<rcs>` issues
>   * Conversions to device-managed APIs (``devm_`` helpers)
>   
>   This is because it is felt that the churn that such changes produce comes
>   at a greater cost than the value of such clean-ups.
>   
>   Conversely, spelling and grammar fixes are not discouraged.
>   
> See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#clean-up-patches

Fine, I don't _need_ to get these accepted. I'll keep this in mind in
future.

It probably came up during some other work when I had to look through use 
of all PCI accessor functions and understand what the callers are trying 
to do. When I took a look at the C file, I ended up noticing other things 
too.

As these are/were not direct requirement for the actual accessor work, I 
tend to send such series separately to avoid complicating review of one or 
the other, feature series tend to be complicated enough even without the 
cleanup patches.

It seems that in the unsent state, these patches predated adding that 
guidance.

-- 
 i.

      reply	other threads:[~2025-06-11  7:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-10 10:32 [PATCH 1/3] cxgb3: Replace PCI related literals with defines & correct variable Ilpo Järvinen
2025-06-10 10:32 ` [PATCH 2/3] cxgb3: Use FIELD_GET() for PCI register fields Ilpo Järvinen
2025-06-10 10:32 ` [PATCH 3/3] cxgb3: Split complex PCI write statement into logic + write Ilpo Järvinen
2025-06-10 20:53 ` [PATCH 1/3] cxgb3: Replace PCI related literals with defines & correct variable Jakub Kicinski
2025-06-11  7:22   ` Ilpo Järvinen [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=a24d9048-d296-9bd5-aa65-4e630dc34d51@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=bharat@chelsio.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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).