linux-kernel - Re: [PATCH] parport: parport_pc: remove double PCI ID for NetMos

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 27 Nov 2013 13:53:22 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	linux-kernel@...r.kernel.org, linux-parport@...ts.infradead.org,
	Maximilian Attems <maks@...o.at>
Subject: Re: [PATCH] parport: parport_pc: remove double PCI ID for NetMos

On Wed, 27 Nov 2013 17:43:43 +0100 Sebastian Andrzej Siewior <bigeasy@...utronix.de> wrote:

> In commit 85747f ("PATCH] parport: add NetMOS 9805 support") Max added
> the PCI ID for NetMOS 9805 based on a Debian bug report from 2k4 which
> was at the v2.4.26 time frame. The patch made into 2.6.14.
> Shortly before that patch akpm merged commit 296d3c783b ("[PATCH] Support
> NetMOS based PCI cards providing serial and parallel ports") which made
> into v2.6.9-rc1.
> Now we have two different entries for the same PCI id.
> I have here the NetMos 9805 which claims to support SPP/EPP/ECP mode.
> This patch takes Max's entry for titan_1284p1 (base != -1 specifies the
> ioport for ECP mode) and replaces akpm's entry for netmos_9805 which
> specified -1 (=none). Both share the same PCI-ID (my card has subsystem
> 0x1000 / 0x0020 so it should match PCI_ANY).
> 
> 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?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/