Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.12 v2] ice/ptp: fix crosstimestamp reporting
Date: Fri,  8 Aug 2025 13:21:08 -0400	[thread overview]
Message-ID: <1754608665-d0efc2d5@stable.kernel.org> (raw)
In-Reply-To: <20250807-ice_crosstimestamp_reporting-v2-1-85746f1cf9f8@blochl.de>

[ Sasha's backport helper bot ]

Hi,

✅ All tests passed successfully. No issues detected.
No action required from the submitter.

The upstream commit SHA1 provided is correct: a5a441ae283d54ec329aadc7426991dc32786d52

WARNING: Author mismatch between patch and upstream commit:
Backport author: Markus Blöchl <markus@blochl.de>
Commit author: Anton Nadezhdin <anton.nadezhdin@intel.com>

Status in newer kernel trees:
6.15.y | Present (different SHA1: f20899b1a877)

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| origin/linux-6.12.y       | Success     | Success    |

      reply	other threads:[~2025-08-08 17:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-07 20:25 [PATCH 6.12 v2] ice/ptp: fix crosstimestamp reporting Markus Blöchl
2025-08-08 17:21 ` Sasha Levin [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=1754608665-d0efc2d5@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=stable@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