From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: "Marek Behún" <kabel@kernel.org>, "Sasha Levin" <sashal@kernel.org>
Subject: Re: [PATCH 5.10.y 3/3] net: dsa: mv88e6xxx: enable .port_set_policy() for 6320 family
Date: Tue, 29 Apr 2025 09:01:20 -0400 [thread overview]
Message-ID: <20250428225051-eb45433926e11814@stable.kernel.org> (raw)
In-Reply-To: <20250428085744.19762-3-kabel@kernel.org>
[ 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: a2ef58e2c4aea4de166fc9832eb2b621e88c98d5
Status in newer kernel trees:
6.14.y | Present (different SHA1: a0898cf9a38d)
6.12.y | Not found
6.6.y | Not found
6.1.y | Not found
5.15.y | Not found
Note: The patch differs from the upstream commit:
---
1: a2ef58e2c4aea < -: ------------- net: dsa: mv88e6xxx: enable .port_set_policy() for 6320 family
-: ------------- > 1: 8fabf354f66fc net: dsa: mv88e6xxx: enable .port_set_policy() for 6320 family
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.15.y | Success | Success |
next prev parent reply other threads:[~2025-04-29 13:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 8:57 [PATCH 5.10.y 1/3] net: dsa: mv88e6xxx: fix atu_move_port_mask for 6341 family Marek Behún
2025-04-28 8:57 ` [PATCH 5.10.y 2/3] net: dsa: mv88e6xxx: enable PVT for 6321 switch Marek Behún
2025-04-29 13:01 ` Sasha Levin
2025-04-28 8:57 ` [PATCH 5.10.y 3/3] net: dsa: mv88e6xxx: enable .port_set_policy() for 6320 family Marek Behún
2025-04-29 13:01 ` Sasha Levin [this message]
2025-04-29 12:49 ` [PATCH 5.10.y 1/3] net: dsa: mv88e6xxx: fix atu_move_port_mask for 6341 family Sasha Levin
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=20250428225051-eb45433926e11814@stable.kernel.org \
--to=sashal@kernel.org \
--cc=kabel@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