linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Valmer Huhn <valmer.huhn@concurrent-rt.com>
Cc: gregkh@linuxfoundation.org, sudip.mukherjee@codethink.co.uk,
	jan.kiszka@siemens.com, linux-serial@vger.kernel.org
Subject: Re: [PATCH] serial: 8250_exar: Fix number of ports for Commtech PCIe cards
Date: Thu, 13 Aug 2020 22:28:45 +0300	[thread overview]
Message-ID: <20200813192845.GJ1891694@smile.fi.intel.com> (raw)
In-Reply-To: <20200813165255.GC345440@icarus.concurrent-rt.com>

On Thu, Aug 13, 2020 at 12:52:55PM -0400, Valmer Huhn wrote:

Thanks for an update, my comments below.

> The following in 8250_exar.c line 589 is used to determine the number
> of ports for each Exar board:
> 
> nr_ports = board->num_ports ? board->num_ports : pcidev->device & 0x0f;
> 
> If the number of ports a card has is not explicitly specified, it defaults
> to the rightmost 4 bits of the PCI device ID. This is prone to error since
> not all PCI device IDs contain a number which corresponds to the number of
> ports that card provides.
> 
> This particular case involves COMMTECH_4222PCIE, COMMTECH_4224PCIE and
> COMMTECH_4228PCIE cards with device IDs 0x0022, 0x0020 and 0x0021.
> Currently the multiport cards receive 2, 0 and 1 port instead of 2, 4 and
> 8 ports respectively.
> 
> To fix this, each Commtech Fastcom PCIe card is given a struct where the
> number of ports is explicitly specified. This ensures 'board->num_ports'
> is used instead of the default 'pcidev->device & 0x0f'.

...

> Fixes: d0aeaa83f0b0 ("serial: exar: split out the exar code from 8250_pci")

> 

Shouldn't be blank line here.

> Signed-off-by: Valmer Huhn <valmer.huhn@concurrent-rt.com>

...

> Tested-by: Valmer Huhn <valmer.huhn@concurrent-rt.com>

This tag (Tested-by: Author_of_the_patch) is implied. We don't want patches
that weren't tested by authors.

After cutter line '---' you missed to provide a changelog along with bumping
patch version. Hint, use -v<X> when run `git format-patch ...`

P.S. Next should be v3, so `git format-patch -v3 ...`.

-- 
With Best Regards,
Andy Shevchenko



      reply	other threads:[~2020-08-13 19:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-13 16:52 [PATCH] serial: 8250_exar: Fix number of ports for Commtech PCIe cards Valmer Huhn
2020-08-13 19:28 ` Andy Shevchenko [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=20200813192845.GJ1891694@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jan.kiszka@siemens.com \
    --cc=linux-serial@vger.kernel.org \
    --cc=sudip.mukherjee@codethink.co.uk \
    --cc=valmer.huhn@concurrent-rt.com \
    /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).