From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Matt Schulte <matts_old@commtech-fastcom.com>
Cc: linux-serial@vger.kernel.org, greg@kroah.com,
Matt Schulte <matts@commtech-fastcom.com>
Subject: Re: [PATCH 2/2] The correct device id for this card is 0x0022.
Date: Wed, 5 Dec 2012 21:38:12 +0000 [thread overview]
Message-ID: <20121205213812.42c61b2e@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <1354740983-4352-2-git-send-email-matts@commtech-fastcom.com>
On Wed, 5 Dec 2012 14:56:22 -0600
Matt Schulte <matts_old@commtech-fastcom.com> wrote:
> Signed-off-by: Matt Schulte <matts@commtech-fastcom.com>
> ---
> Built against tty-next commit: b0ab02361167faa82198b783a8d555eb6f58901c
>
> drivers/tty/serial/8250/8250_pci.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/tty/serial/8250/8250_pci.c b/drivers/tty/serial/8250/8250_pci.c
> index bf2f1a0..777832c 100644
> --- a/drivers/tty/serial/8250/8250_pci.c
> +++ b/drivers/tty/serial/8250/8250_pci.c
> @@ -1301,7 +1301,7 @@ pci_wch_ch353_setup(struct serial_private *priv,
> #define PCI_VENDOR_ID_AGESTAR 0x5372
> #define PCI_DEVICE_ID_AGESTAR_9375 0x6872
> #define PCI_VENDOR_ID_ASIX 0x9710
> -#define PCI_DEVICE_ID_COMMTECH_4222PCIE 0x0019
> +#define PCI_DEVICE_ID_COMMTECH_4222PCIE 0x0022
> #define PCI_DEVICE_ID_COMMTECH_4224PCIE 0x0020
> #define PCI_DEVICE_ID_COMMTECH_4228PCIE 0x0021
Can you keep them in order 8)
next prev parent reply other threads:[~2012-12-05 21:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 20:56 [PATCH 1/2] pbn_b0_8_1152000_200 is supposed to be an 8 port definition Matt Schulte
2012-12-05 20:56 ` [PATCH 2/2] The correct device id for this card is 0x0022 Matt Schulte
2012-12-05 21:38 ` Alan Cox [this message]
2012-12-05 22:20 ` Will Fagan
2013-01-16 2:59 ` Greg KH
2013-01-16 3:00 ` Greg KH
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=20121205213812.42c61b2e@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=linux-serial@vger.kernel.org \
--cc=matts@commtech-fastcom.com \
--cc=matts_old@commtech-fastcom.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