From: Andrey Panin <pazke@orbita1.ru>
To: Russell King <rmk@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Q] 2.4.6 compatibility cruft in 8250_pci.c
Date: Mon, 14 Oct 2002 12:11:23 +0400 [thread overview]
Message-ID: <20021014081123.GA338@pazke.ipt> (raw)
In-Reply-To: <20021011132723.B8823@flint.arm.linux.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1058 bytes --]
On Птн, Окт 11, 2002 at 01:27:23 +0100, Russell King wrote:
> On Wed, Oct 09, 2002 at 07:41:43AM +0400, Andrey Panin wrote:
> > Ugh, this is not what i need. I want to move SIIG combo cards support
> > from 8250_pci.c to parport_serial.c module. For this I need to export
> > pci_siig[12]0x_fn() functions having struct pci_board *board as one
> > of arguments. parport_serial.c modules already includes
> > <linux/serialP.h> so used it for 2.4, but 2.5 is different.
>
> Well, I'd like to eliminate struct pci_board from the init functions
> for several reasons. One of them is that some of the init functions
> do buggy things with it (like increasing the number of ports.)
>
> This should solve your problem - please confirm.
>
Yes it should fix my problem, actually SIIG initialization functions don't
even use this argument.
When you submit this change to 2.5 I'll send a patch ASAP.
Best regards.
--
Andrey Panin | Embedded systems software engineer
pazke@orbita1.ru | PGP key: wwwkeys.eu.pgp.net
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next parent reply other threads:[~2002-10-14 8:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20021009004606.G12270@flint.arm.linux.org.uk>
[not found] ` <57751.172.192.100.207.1034134903.squirrel@mail.orbita1.ru>
[not found] ` <20021011132723.B8823@flint.arm.linux.org.uk>
2002-10-14 8:11 ` Andrey Panin [this message]
2002-10-06 0:14 [Q] 2.4.6 compatibility cruft in 8250_pci.c Andrey Panin
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=20021014081123.GA338@pazke.ipt \
--to=pazke@orbita1.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).