From: Greg KH <gregkh@linuxfoundation.org>
To: Guan Yung Tseng <guan.yung.tseng@ni.com>
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 8250_pci.c: Update NI specific devices class to multi serial
Date: Fri, 18 Jan 2019 12:57:18 +0100 [thread overview]
Message-ID: <20190118115718.GA16370@kroah.com> (raw)
In-Reply-To: <1547475005-23435-1-git-send-email-guan.yung.tseng@ni.com>
On Mon, Jan 14, 2019 at 10:10:05PM +0800, Guan Yung Tseng wrote:
> Modified NI devices class to PCI_CLASS_COMMUNICATION_MULTISERIAL.
> The reason of doing this is because all NI multi port serial cards
> use PCI_CLASS_COMMUNICATION_OTHER class and thus fail the
> serial_pci_is_class_communication test added in the commit 7d8905d06405
> ("serial: 8250_pci: Enable device after we check black list").
>
> Signed-off-by: Guan Yung Tseng <guan.yung.tseng@ni.com>
> ---
> drivers/tty/serial/8250/8250_pci.c | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
>
> diff --git a/drivers/tty/serial/8250/8250_pci.c b/drivers/tty/serial/8250/8250_pci.c
> index 4986b4a..0949db1 100644
> --- a/drivers/tty/serial/8250/8250_pci.c
> +++ b/drivers/tty/serial/8250/8250_pci.c
> @@ -663,6 +663,13 @@ static int pci_xircom_init(struct pci_dev *dev)
> return 0;
> }
>
> +static int pci_ni_probe(struct pci_dev *dev)
> +{
> + dev->class = PCI_CLASS_COMMUNICATION_MULTISERIAL << 8 |
> + (dev->class & 0xff);
As Christoph said, this looks really odd. This field comes from the
PCI structure on the device, it should not be modified by the kernel.
Unless the device is broken and needs to be fixed up in the kernel?
Also, you have sent 2 different patches here for this type of issue, are
both needed? If so, please resend both of them as a patch series, with
more explainations in this one as to why you are modifying this field.
I've dropped all pending patches from you from my queue now.
thanks,
greg k-h
next prev parent reply other threads:[~2019-01-18 11:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 14:10 [PATCH] 8250_pci.c: Update NI specific devices class to multi serial Guan Yung Tseng
2019-01-18 11:57 ` Greg KH [this message]
2019-01-22 11:55 ` Heikki Krogerus
2019-01-23 14:11 ` Andy Shevchenko
2019-01-23 15:18 ` Andy Shevchenko
2019-01-23 16:06 ` Andy Shevchenko
[not found] ` <d24b4177fda84042b4f59f2bb77e149e@atfkex01.bachmann.at>
2019-01-24 22:47 ` Andy Shevchenko
2019-01-28 8:04 ` Guan Yung Tseng
-- strict thread matches above, loose matches on Subject: below --
2019-01-24 7:07 Guan Yung Tseng
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=20190118115718.GA16370@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=guan.yung.tseng@ni.com \
--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