All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, linux-parport@lists.infradead.org,
	Maximilian Attems <maks@stro.at>
Subject: Re: [PATCH] parport: parport_pc: remove double PCI ID for NetMos
Date: Thu, 28 Nov 2013 11:35:11 +0100	[thread overview]
Message-ID: <52971C5F.7040307@linutronix.de> (raw)
In-Reply-To: <20131127135322.49ea91c23db4879f97b524f0@linux-foundation.org>

On 11/27/2013 10:53 PM, Andrew Morton wrote:
>> While here I also drop the entry for titan_1284p2 which is the same as
>> netmos_9815.
> 
> Does this change have any runtime-visible effects?

Titan p2 used to specify class + subclass which is now replaced with
PCI_ID_ANY, I doubt this makes any difference at all.

The only runtime visible change I notice is with KERN_DEBUG being
visible. The card details are the same, it always prints

|parport1: PC-style at 0xc120 (0xc128), irq 11, using FIFO
[PCSPP,TRISTATE,COMPAT,ECP]

However the ID that was used to detect the card is different:

| PCI parallel port detected: 1415:c118, I/O at 0xc120(0xc128), IRQ 11

vs

| PCI parallel port detected: 9710:9805, I/O at 0xc120(0xc128), IRQ 11

The wrong id print is printed for all devices which come after
PCI_DEVICE_ID_OXSEMI_PCIe840_G in the id table because the code that
prints the ID table assumes one id per entry.

So we could
- drop printk
- use id->vendor + id->device instead
- do the last item + remove parport_pc_pci_cards and pass the data
  struct as data.
- nothing

any preferences?

Sebastian

  reply	other threads:[~2013-11-28 10:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-27 16:43 [PATCH] parport: parport_pc: remove double PCI ID for NetMos Sebastian Andrzej Siewior
2013-11-27 21:53 ` Andrew Morton
2013-11-28 10:35   ` Sebastian Andrzej Siewior [this message]
2013-12-02 21:44     ` Andrew Morton

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=52971C5F.7040307@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parport@lists.infradead.org \
    --cc=maks@stro.at \
    /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.