From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Anders Blomdell <anders.blomdell@control.lth.se>
Cc: linux-serial@vger.kernel.org
Subject: Re: kernel 5.19.8: "Oxford Semiconductor Ltd OXPCIe952 Dual Native 950 UART" gets wrong baudrate (PCI ID 1415:c158)
Date: Tue, 13 Sep 2022 10:21:45 +0200 [thread overview]
Message-ID: <YyA9maUOlPIExIUd@kroah.com> (raw)
In-Reply-To: <ef8fd762-88cf-548a-0599-17d939ad3a57@control.lth.se>
On Mon, Sep 12, 2022 at 09:59:08PM +0200, Anders Blomdell wrote:
> Reverting commits
> 366f6c955d4d1a5125ffcd6875ead26a3c7a2a1c
> 9c5c8aaed50bf3478073ab51b8b1f3f5327d3cfa
> fixes my problems.
What problems exactly?
And why not cc: the developers of those commits?
thanks,
greg k-h
next prev parent reply other threads:[~2022-09-13 8:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 19:59 kernel 5.19.8: "Oxford Semiconductor Ltd OXPCIe952 Dual Native 950 UART" gets wrong baudrate (PCI ID 1415:c158) Anders Blomdell
2022-09-13 8:21 ` Greg Kroah-Hartman [this message]
2022-09-13 12:16 ` Anders Blomdell
2022-09-13 12:30 ` Greg Kroah-Hartman
2022-09-13 12:43 ` Anders Blomdell
2022-09-13 14:01 ` Greg Kroah-Hartman
2022-09-13 15:34 ` Anders Blomdell
2022-09-13 16:19 ` Maciej W. Rozycki
2022-09-13 17:17 ` Anders Blomdell
2022-09-16 21:50 ` Maciej W. Rozycki
2022-09-13 18:59 ` Anders Blomdell
2022-09-13 21:07 ` Anders Blomdell
2022-09-14 0:00 ` Maciej W. Rozycki
2022-09-14 11:01 ` Anders Blomdell
2022-09-14 11:41 ` Maciej W. Rozycki
2022-09-14 14:15 ` Maciej W. Rozycki
2022-09-14 14:22 ` Anders Blomdell
2022-09-16 21:03 ` Maciej W. Rozycki
2022-09-19 6:50 ` Anders Blomdell
2022-09-14 14:57 ` Greg Kroah-Hartman
2022-09-15 10:09 ` Anders Blomdell
2022-09-16 21:03 ` Maciej W. Rozycki
2022-10-04 20:39 ` Grant Edwards
2022-10-04 21:14 ` Grant Edwards
2022-10-05 10:02 ` Ilpo Järvinen
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=YyA9maUOlPIExIUd@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=anders.blomdell@control.lth.se \
--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