From: Sasha Levin <sashal@kernel.org>
To: "Csókás Bence" <csokas.bence@prolan.hu>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 6.6 1/3] net: fec: Move `fec_ptp_read()` to the top of the file
Date: Sat, 23 Nov 2024 09:36:26 -0500 [thread overview]
Message-ID: <Z0HoasOBIo1y_vjc@sashalap> (raw)
In-Reply-To: <30b031c5-b3f4-44e4-9217-c364651ab28e@prolan.hu>
On Fri, Nov 22, 2024 at 02:56:40PM +0100, Csókás Bence wrote:
>Hi,
>
>On 2024. 11. 22. 14:51, Sasha Levin wrote:
>>[ Sasha's backport helper bot ]
>>
>>Hi,
>>
>>Found matching upstream commit: 4374a1fe580a14f6152752390c678d90311df247
>>
>>WARNING: Author mismatch between patch and found commit:
>>Backport author: =?UTF-8?q?Cs=C3=B3k=C3=A1s=2C=20Bence?= <csokas.bence@prolan.hu>
>>Commit author: Csókás, Bence <csokas.bence@prolan.hu>
>>
>>
>>Status in newer kernel trees:
>>6.12.y | Present (exact SHA1)
>>6.11.y | Present (different SHA1: 97f35652e0e8)
>>6.6.y | Present (different SHA1: 1e1eb62c40e1)
>
>1/3 and 2/3 of this series was already applied by Greg, only 3/3 was not.
>
>commit: bf8ca67e2167 ("net: fec: refactor PPS channel configuration")
Dare I ask why we need it to begin with? Commit message says:
Preparation patch to allow for PPS channel configuration, no functional
change intended.
--
Thanks,
Sasha
next prev parent reply other threads:[~2024-11-23 14:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 6:41 [REQUEST] net: fec: Not yet ported PTP patches Csókás Bence
2024-10-16 8:01 ` [PATCH 6.6 1/3] net: fec: Move `fec_ptp_read()` to the top of the file Csókás, Bence
2024-11-22 13:51 ` Sasha Levin
2024-11-22 13:56 ` Csókás Bence
2024-11-23 14:36 ` Sasha Levin [this message]
2024-11-24 10:47 ` Csókás Bence
2024-11-24 12:06 ` Sasha Levin
2024-10-16 8:01 ` [PATCH 6.6 2/3] net: fec: Remove duplicated code Csókás, Bence
2024-10-16 8:01 ` [PATCH 6.6 3/3] net: fec: refactor PPS channel configuration Csókás, Bence
2024-10-18 10:37 ` Greg Kroah-Hartman
2024-11-22 9:10 ` Csókás Bence
2024-11-22 11:04 ` Greg Kroah-Hartman
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=Z0HoasOBIo1y_vjc@sashalap \
--to=sashal@kernel.org \
--cc=csokas.bence@prolan.hu \
--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