Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Patrick Fischer <admin@tsv-stahl-riesa.de>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
	Jiri Slaby <jirislaby@kernel.org>,
	Thierry Reding <thierry.reding@kernel.org>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	Shardar Shariff Md <smohammed@nvidia.com>,
	Krishna Yarlagadda <kyarlagadda@nvidia.com>,
	Svyatoslav Ryhel <clamor95@gmail.com>,
	linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
	linux-tegra@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 0/2] serial: tegra: Fix 32-bit overflows in the clock rate adjustment
Date: Sun, 22 Nov 2026 10:46:36 +0100	[thread overview]
Message-ID: <2026112227-uphill-footnote-1781@gregkh> (raw)
In-Reply-To: <e3b302d3-979d-4b7e-9b51-dd5c8121c192@tsv-stahl-riesa.de>

On Sun, Nov 22, 2026 at 10:42:34AM +0100, Patrick Fischer wrote:
> Hi Greg,
> 
> gentle ping on this series now that the merge window is over. Both
> patches have Tested-by and Reviewed-by from Svyatoslav and still apply
> cleanly to 7.4-rc3. Please let me know if anything needs to change.

There is no context here :(


  reply	other threads:[~2026-11-22  9:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-25 22:50 [PATCH 0/2] serial: tegra: Fix 32-bit overflows in the clock rate adjustment Patrick Fischer via B4 Relay
2026-10-25 22:50 ` [PATCH 1/2] serial: tegra: Fix overflow in tegra_get_tolerance_rate() Patrick Fischer via B4 Relay
2026-10-26  8:50   ` Svyatoslav Ryhel
2026-10-25 22:50 ` [PATCH 2/2] serial: tegra: Fix overflow in tegra_check_rate_in_range() Patrick Fischer via B4 Relay
2026-10-26  8:50   ` Svyatoslav Ryhel
2026-11-22  9:42 ` [PATCH 0/2] serial: tegra: Fix 32-bit overflows in the clock rate adjustment Patrick Fischer
2026-11-22  9:46   ` Greg Kroah-Hartman [this message]
2026-11-22 10:13 ` Patrick Fischer

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=2026112227-uphill-footnote-1781@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=admin@tsv-stahl-riesa.de \
    --cc=clamor95@gmail.com \
    --cc=jirislaby@kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=kyarlagadda@nvidia.com \
    --cc=ldewangan@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=smohammed@nvidia.com \
    --cc=stable@vger.kernel.org \
    --cc=thierry.reding@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