From: Bjorn Helgaas <helgaas@kernel.org>
To: Cameron Williams <cang1@live.co.uk>
Cc: bhelgaas@google.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
sudipm.mukherjee@gmail.com, gregkh@linuxfoundation.org
Subject: Re: [PATCH 1/4] PCI: Add device IDs for Brainboxes/Intashield PX/UC/UP cards
Date: Thu, 21 Sep 2023 16:58:22 -0500 [thread overview]
Message-ID: <20230921215822.GA347672@bhelgaas> (raw)
In-Reply-To: <DU0PR02MB789950E64D808DB57E9D7312C4F8A@DU0PR02MB7899.eurprd02.prod.outlook.com>
On Thu, Sep 21, 2023 at 10:09:16PM +0100, Cameron Williams wrote:
> Add device IDs for PCI/PCIe serial cards manufactured by
> Brainboxes (IS/IX/UC/UP/PX).
> Apologies if this file isn't strictly for your tree. All trees
> I am sending this patch series to use these PCI IDs, I was unsure
> if this was the correct way to go about it, and better safe than
> sorry. Thank you for understanding and please disregard if
> its not required.
From the top of the file:
* Do not add new entries to this file unless the definitions
* are shared between multiple drivers.
I can't tell whether that applies here since I haven't seen the other
patches. If they're only used in one file, you can add the #define to
that file or use the bare hex values. This reduces merge conflicts in
pci_ids.h when backporting things.
Also it looks like there's a mix of tab vs space indentation below.
They should all be tabs before the device ID and it looks like a
single space before the comment.
> +#define PCI_DEVICE_ID_INTASHIELD_UC246 0x0aa1 /* Revision 2*/
> +#define PCI_DEVICE_ID_INTASHIELD_UC246R3 0x0aa2 /* Revision 3 */
Comment indentation error.
> +#define PCI_DEVICE_ID_INTASHIELD_PX803R3 0x401e /* Revision 3 */
> +#define PCI_DEVICE_ID_INTASHIELD_PX475LPT 0x401f /* LPT port */
Indentation error.
next prev parent reply other threads:[~2023-09-21 22:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 21:09 [PATCH 1/4] PCI: Add device IDs for Brainboxes/Intashield PX/UC/UP cards Cameron Williams
2023-09-21 21:58 ` Bjorn Helgaas [this message]
2023-09-22 5:53 ` Cameron Williams
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=20230921215822.GA347672@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=cang1@live.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=sudipm.mukherjee@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 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.