From: Jiri Slaby <jirislaby@kernel.org>
To: Cameron Williams <cang1@live.co.uk>,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org
Subject: Re: [PATCH v3 1/7] tty: 8250: Fix IS-200 PCI ID comment
Date: Mon, 16 Oct 2023 07:37:43 +0200 [thread overview]
Message-ID: <17636fae-6aad-4f6f-bd16-6296e726b324@kernel.org> (raw)
In-Reply-To: <DU0PR02MB78991BB41F77731BF0BDD777C4D0A@DU0PR02MB7899.eurprd02.prod.outlook.com>
On 15. 10. 23, 19:10, Cameron Williams wrote:
> Fix the PCI comment for the IS-200 card. The PCI ID for the IS-200
> is 0x0d80, and the definition used (PCI_DEVICE_ID_INTASHIELD_IS200)
> is indeed 0x0d80, clarify that by fixing the comment as its
> neighbouring cards are all at 0x0020 offsets.
The real question is why to maintain a comment here at all? I suggest
dropping them both instead.
> Signed-off-by: Cameron Williams <cang1@live.co.uk>
> ---
> v2 - v3:
> Clarify commit message with better explanation of the change.
> Re-submit patch series using git send-email to make threading work.
>
> v1 - v2:
> This is a resubmission series for the patch series below. That series
> was lots of changes sent to lots of maintainers, this series is just for
> the tty/serial/8250 subsystem.
>
> [1] https://lore.kernel.org/all/DU0PR02MB789950E64D808DB57E9D7312C4F8A@DU0PR02MB7899.eurprd02.prod.outlook.com/
> [2] https://lore.kernel.org/all/DU0PR02MB7899DE53DFC900EFB50E53F2C4F8A@DU0PR02MB7899.eurprd02.prod.outlook.com/
> [3] https://lore.kernel.org/all/DU0PR02MB7899033E7E81EAF3694BC20AC4F8A@DU0PR02MB7899.eurprd02.prod.outlook.com/
> [4] https://lore.kernel.org/all/DU0PR02MB7899EABA8C3DCAC94DCC79D4C4F8A@DU0PR02MB7899.eurprd02.prod.outlook.com/
>
> drivers/tty/serial/8250/8250_pci.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/tty/serial/8250/8250_pci.c b/drivers/tty/serial/8250/8250_pci.c
> index 62a9bd30b4db..ecb4e9acc70d 100644
> --- a/drivers/tty/serial/8250/8250_pci.c
> +++ b/drivers/tty/serial/8250/8250_pci.c
> @@ -4917,7 +4917,7 @@ static const struct pci_device_id serial_pci_tbl[] = {
> * IntaShield IS-200
> */
> { PCI_VENDOR_ID_INTASHIELD, PCI_DEVICE_ID_INTASHIELD_IS200,
> - PCI_ANY_ID, PCI_ANY_ID, 0, 0, /* 135a.0811 */
> + PCI_ANY_ID, PCI_ANY_ID, 0, 0, /* 135a.0d80 */
> pbn_b2_2_115200 },
> /*
> * IntaShield IS-400
thanks,
--
js
suse labs
next prev parent reply other threads:[~2023-10-16 5:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BBPatchesV3>
2023-10-15 17:10 ` [PATCH v3 0/7] Brainboxes serial cards additions/fixes Cameron Williams
[not found] ` <20231015171141.3309-1-cang1@live.co.uk>
2023-10-15 17:10 ` [PATCH v3 1/7] tty: 8250: Fix IS-200 PCI ID comment Cameron Williams
2023-10-16 5:37 ` Jiri Slaby [this message]
2023-10-16 7:29 ` Cameron Williams
2023-10-15 17:10 ` [PATCH v3 2/7] tty: 8250: Add support for additional Brainboxes UC cards Cameron Williams
2023-10-16 5:40 ` Jiri Slaby
2023-10-16 7:34 ` Cameron Williams
2023-10-15 17:10 ` [PATCH v3 3/7] tty: 8250: Add support for Brainboxes UP cards Cameron Williams
2023-10-16 5:40 ` Jiri Slaby
2023-10-15 17:10 ` [PATCH v3 4/7] tty: 8250: Add support for Intashield IS-100 Cameron Williams
2023-10-16 5:40 ` Jiri Slaby
2023-10-15 17:10 ` [PATCH v3 5/7] tty: 8250: Add support for and fix up additional Brainboxes PX cards Cameron Williams
2023-10-16 5:41 ` Jiri Slaby
2023-10-15 17:10 ` [PATCH v3 6/7] tty: 8250: Add support for Intashield IX cards Cameron Williams
2023-10-16 5:42 ` Jiri Slaby
2023-10-15 17:10 ` [PATCH v3 7/7] tty: 8250: Add Brainboxes Oxford Semiconductor-based quirks Cameron Williams
2023-10-16 5:44 ` Jiri Slaby
2023-10-16 7:36 ` 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=17636fae-6aad-4f6f-bd16-6296e726b324@kernel.org \
--to=jirislaby@kernel.org \
--cc=cang1@live.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox