From: Richard Leitner <richard.leitner@linux.dev>
To: "David R. Piegdon" <david@p23q.org>
Cc: "Randolph Maaßen" <randolph.maassen@indurad.com>,
linux-tegra@vger.kernel.org, "Dmitry Osipenko" <digetx@gmail.com>,
"Mikko Perttunen" <mperttunen@nvidia.com>,
"Nicolas Chauvet" <kwizart@gmail.com>,
"Jiri Slaby" <jirislaby@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] serial8250 on tegra hsuart: recover from spurious interrupts due to tegra2 silicon bug
Date: Thu, 22 Dec 2022 08:07:06 +0100 [thread overview]
Message-ID: <Y6QCGuXXavQwnR/7@g0hl1n.net> (raw)
In-Reply-To: <73C64EC3-3F03-426F-833B-CC9FBA9205D8@p23q.org>
Hi,
On Tue, Nov 22, 2022 at 06:47:39PM +0100, David R. Piegdon wrote:
> Hallo Richard,
> it's great to hear that the patch was helpful for someone other than us.
> However, I no longer work on that project, or that company. I have added my old coworker Randolph to the recipients, who, I think, still maintains that platform (based on colibri t20 from toradex). Maybe he can be of help. If you come up with technical questions, I might still have a memory or two.
Thanks for the feedback.
As I'd love to see this mainline: Does one of you (David, Randolph) have
interest/time to try to bring this mainline? If not I can try, altough
I'm not into the Tegra UARTs details that deep...
regards;rl
> @Randolph: Cheers & I hope everything is going well!
>
> Yours,
> David
>
next prev parent reply other threads:[~2022-12-22 7:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4676ea34-69ce-5422-1ded-94218b89f7d9@p23q.org>
2022-11-21 10:35 ` Richard Leitner
[not found] ` <73C64EC3-3F03-426F-833B-CC9FBA9205D8@p23q.org>
2022-12-22 7:07 ` Richard Leitner [this message]
2022-12-22 10:30 ` 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=Y6QCGuXXavQwnR/7@g0hl1n.net \
--to=richard.leitner@linux.dev \
--cc=david@p23q.org \
--cc=digetx@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=kwizart@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mperttunen@nvidia.com \
--cc=randolph.maassen@indurad.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
all inboxes | Powered by JetHome®