From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Jay Dolan <jay.dolan@accesio.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"open list:SERIAL DRIVERS" <linux-serial@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jiri Slaby <jirislaby@kernel.org>
Subject: Re: [PATCH v2 0/2] serial: 8250_pci patches to address issues with pericom_do_set_divisor()
Date: Mon, 22 Nov 2021 13:55:06 +0200 [thread overview]
Message-ID: <YZuFGik6oinuTX3z@smile.fi.intel.com> (raw)
In-Reply-To: <CAHp75VcboxaNnSnt1wKvE9JefSsLtMReZkMDVEpUVOJnd_oQnA@mail.gmail.com>
On Thu, Nov 18, 2021 at 11:52:06AM +0200, Andy Shevchenko wrote:
> On Thu, Nov 18, 2021 at 8:09 AM Jay Dolan <jay.dolan@accesio.com> wrote:
> > On 11/17/21 6:55 AM, Andy Shevchenko wrote:
...
> > > Jay, can you retest this, please?
> > I was able to verify that the fourth port was placed at the fixed
> > address for the card that previously had it at the wrong offset.
> > I was also able to verify all of the standard baud rates for 24 and
> > 14.7456 MHz crystals from 50 to their respective uartclk speed on the
> > oscilloscope.
>
> Thanks!
Greg, there is a subtle bug found in the second patch, I'll issue the v2 soon.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2021-11-22 11:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 14:55 [PATCH v2 0/2] serial: 8250_pci patches to address issues with pericom_do_set_divisor() Andy Shevchenko
2021-11-17 14:55 ` [PATCH v2 1/2] serial: 8250_pci: Fix ACCES entries in pci_serial_quirks array Andy Shevchenko
2021-11-17 14:55 ` [PATCH v2 2/2] serial: 8250_pci: rewrite pericom_do_set_divisor() Andy Shevchenko
2021-11-18 4:16 ` [PATCH v2 0/2] serial: 8250_pci patches to address issues with pericom_do_set_divisor() Jay Dolan
2021-11-18 9:52 ` Andy Shevchenko
2021-11-22 11:55 ` 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=YZuFGik6oinuTX3z@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jay.dolan@accesio.com \
--cc=jirislaby@kernel.org \
--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 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.