From: Bjorn Helgaas <helgaas@kernel.org>
To: Puranjay Mohan <puranjay12@gmail.com>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
Bjorn Helgaas <bjorn@helgaas.com>,
netdev <netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 3/3] net: fddi: skfp: Remove unused private PCI definitions
Date: Thu, 20 Jun 2019 16:37:21 -0500 [thread overview]
Message-ID: <20190620213721.GD110859@google.com> (raw)
In-Reply-To: <20190620180754.15413-4-puranjay12@gmail.com>
On Thu, Jun 20, 2019 at 11:37:54PM +0530, Puranjay Mohan wrote:
> Remove unused and private PCI definitions from skfbi.h because generic PCI
> symbols are already included from pci_regs.h.
>
> Signed-off-by: Puranjay Mohan <puranjay12@gmail.com>
> ---
> drivers/net/fddi/skfp/h/skfbi.h | 207 +-------------------------------
> 1 file changed, 1 insertion(+), 206 deletions(-)
>
> diff --git a/drivers/net/fddi/skfp/h/skfbi.h b/drivers/net/fddi/skfp/h/skfbi.h
> index a05ce16171be..a8af80148022 100644
> --- a/drivers/net/fddi/skfp/h/skfbi.h
> +++ b/drivers/net/fddi/skfp/h/skfbi.h
> @@ -27,46 +27,6 @@
> /*
> * Configuration Space header
> */
This comment should be removed because it goes along with the
definitions below (the ones from PCI_VENDOR_ID to PCI_MAX_LAT).
> -#define PCI_VENDOR_ID 0x00 /* 16 bit Vendor ID */
> -#define PCI_DEVICE_ID 0x02 /* 16 bit Device ID */
> @@ -74,179 +34,14 @@
> * Note: The temperature and voltage sensors are relocated on a different
> * I2C bus.
> */
> -#define I2C_ADDR_VPD 0xA0 /* I2C address for the VPD EEPROM */
> +#define I2C_ADDR_VPD 0xA0 /* I2C address for the VPD EEPROM */
You removed the space at the end of the I2C_ADDR_VPD line. That space
*is* a whitespace error, but generally you should avoid fixing random
unrelated issues in the middle of your patch. Those random fixes make
it harder because the reviewer is expecting to see unused PCI-related
things removed and seeing an I2C diff is surprising and forces him/her
to do some investigation.
> -/* PCI_STATUS 16 bit Status */
> #define PCI_PERR 0x8000 /* Bit 15: Parity Error */
> #define PCI_SERR 0x4000 /* Bit 14: Signaled SERR */
> #define PCI_RMABORT 0x2000 /* Bit 13: Received Master Abort */
These should be replaced by PCI_STATUS_DETECTED_PARITY and similar
generic definitions. You could do this in your 1/1 patch along with
PCI_REVISION_ID.
> -#define PCI_RTABORT 0x1000 /* Bit 12: Received Target Abort */
> #define PCI_STABORT 0x0800 /* Bit 11: Sent Target Abort */
> -#define PCI_DEVSEL 0x0600 /* Bit 10..9: DEVSEL Timing */
> -#define PCI_DEV_FAST (0<<9) /* fast */
> -#define PCI_DEV_MEDIUM (1<<9) /* medium */
> -#define PCI_DEV_SLOW (2<<9) /* slow */
> #define PCI_DATAPERR 0x0100 /* Bit 8: DATA Parity error detected */
> -#define PCI_FB2BCAP 0x0080 /* Bit 7: Fast Back-to-Back Capability */
> -#define PCI_UDF 0x0040 /* Bit 6: User Defined Features */
> -#define PCI_66MHZCAP 0x0020 /* Bit 5: 66 MHz PCI bus clock capable */
> -#define PCI_NEWCAP 0x0010 /* Bit 4: New cap. list implemented */
> -
> #define PCI_ERRBITS (PCI_PERR|PCI_SERR|PCI_RMABORT|PCI_STABORT|PCI_DATAPERR)
next prev parent reply other threads:[~2019-06-20 21:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 18:07 [PATCH v2 0/3] net: fddi: skfp: Use PCI generic definitions instead of private duplicates Puranjay Mohan
2019-06-20 18:07 ` [PATCH v2 1/3] net: fddi: skfp: Rename PCI_REV_ID to PCI_REVISION_ID Puranjay Mohan
2019-06-24 6:45 ` Christoph Hellwig
2019-06-20 18:07 ` [PATCH v2 2/3] net: fddi: skfp: Include generic PCI definitions Puranjay Mohan
2019-06-20 21:37 ` Bjorn Helgaas
2019-06-20 18:07 ` [PATCH v2 3/3] net: fddi: skfp: Remove unused private " Puranjay Mohan
2019-06-20 21:37 ` Bjorn Helgaas [this message]
2019-06-20 18:37 ` [PATCH v2 0/3] net: fddi: skfp: Use PCI generic definitions instead of private duplicates Stephen Hemminger
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=20190620213721.GD110859@google.com \
--to=helgaas@kernel.org \
--cc=bjorn@helgaas.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=puranjay12@gmail.com \
--cc=skhan@linuxfoundation.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).