From: Greg KH <gregkh@linuxfoundation.org>
To: Peter Hung <hpeter@gmail.com>
Cc: jslaby@suse.cz, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org,
Peter Hung <hpeter+linux_kernel@gmail.com>
Subject: Re: [PATCH] serial: fix io address assign method with Fintek PCI-to-UART Product
Date: Tue, 18 Nov 2014 19:45:18 -0800 [thread overview]
Message-ID: <20141119034518.GB15293@kroah.com> (raw)
In-Reply-To: <1416364553-29982-1-git-send-email-hpeter+linux_kernel@gmail.com>
On Wed, Nov 19, 2014 at 10:35:53AM +0800, Peter Hung wrote:
> The original driver fixed the io address with 0xe000+idx*8, but real io address assigned from BIOS
> is dynamically from read PCI configure space 0x24, 0x20, 0x1c.
>
> The Fintek F81504/F81508/F81512 maybe malfunction without this patch and malfunction surely when
> more the 1 PCI card.
Please wrap these lines at 72 columns please, like git wants you to.
>
> Signed-off-by: Peter Hung <hpeter+linux_kernel@gmail.com>
> ---
> drivers/tty/serial/8250/8250_pci.c | 63 ++++++++++++++++++++++++++++----------
> 1 file changed, 47 insertions(+), 16 deletions(-)
>
> diff --git a/drivers/tty/serial/8250/8250_pci.c b/drivers/tty/serial/8250/8250_pci.c
> index 0468e15..6dfa227 100644
> --- a/drivers/tty/serial/8250/8250_pci.c
> +++ b/drivers/tty/serial/8250/8250_pci.c
> @@ -1551,28 +1551,51 @@ static int pci_fintek_setup(struct serial_private *priv,
> {
> struct pci_dev *pdev = priv->dev;
> unsigned long base;
> - unsigned long iobase;
> + unsigned long iobase = 0;
Why initialize this to 0? That shouldn't be needed as you set it later
in the function before you use it, right?
Care to try again?
thanks,
greg k-h
prev parent reply other threads:[~2014-11-19 3:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 2:35 [PATCH] serial: fix io address assign method with Fintek PCI-to-UART Product Peter Hung
2014-11-19 3:45 ` Greg KH [this message]
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=20141119034518.GB15293@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=hpeter+linux_kernel@gmail.com \
--cc=hpeter@gmail.com \
--cc=jslaby@suse.cz \
--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