All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: udknight@gmail.com
Cc: Greg KH <gregkh@linuxfoundation.org>,
	jslaby@suse.cz, alan@linux.intel.com, matts@commtech-fastcom.com,
	wfp5p@virginia.edu, tklauser@distanz.ch,
	linux-serial@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: [v3.9] [v3.10] [Regression]  serial: 8250_pci: add support for another kind of NetMos Technology PCI 9835 Multi-I/O Controller
Date: Mon, 01 Jul 2013 12:14:45 -0400	[thread overview]
Message-ID: <51D1AAF5.5050004@canonical.com> (raw)

Hi Wang,

A bug was opened against the Ubuntu kernel[0].  After a kernel bisect,
it was found that reverting the following commit resolved this bug:

commit 8d2f8cd424ca0b99001f3ff4f5db87c4e525f366
Author: Wang YanQing <udknight@gmail.com>
Date:   Fri Mar 1 11:47:20 2013 +0800

    serial: 8250_pci: add support for another kind of NetMos Technology
PCI 9835 Multi-I/O Controller


The regression was introduced as of v3.9-rc3 and still exists in the
current Mainline tree.  It was also propagated to the stable trees.

The patch causes the device to use the serial module instead of
parport_serial.  Maybe the the quirk in ~drivers/pci/quirks.c
quirk_netmos() needs to be modified?

I see that you are the author of this patch, so I wanted to run this by
you.  I was thinking of requesting a revert, but I wanted to get your
feedback first.


Thanks,

Joe


             reply	other threads:[~2013-07-01 16:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-01 16:14 Joseph Salisbury [this message]
2013-07-01 16:27 ` [v3.9] [v3.10] [Regression] serial: 8250_pci: add support for another kind of NetMos Technology PCI 9835 Multi-I/O Controller Greg KH
2013-07-01 18:48   ` Joseph Salisbury
2013-07-02  4:46 ` Wang YanQing

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=51D1AAF5.5050004@canonical.com \
    --to=joseph.salisbury@canonical.com \
    --cc=alan@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=matts@commtech-fastcom.com \
    --cc=tklauser@distanz.ch \
    --cc=udknight@gmail.com \
    --cc=wfp5p@virginia.edu \
    /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.