From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.4.y 2/6] net_sched: sch_sfq: handle bigger packets
Date: Thu, 17 Jul 2025 21:34:30 -0400 [thread overview]
Message-ID: <1752797234-97c617e8@stable.kernel.org> (raw)
In-Reply-To: <20250717124556.589696-3-harshit.m.mogalapalli@oracle.com>
[ 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: e4650d7ae4252f67e997a632adfae0dd74d3a99a
WARNING: Author mismatch between patch and upstream commit:
Backport author: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
Commit author: Eric Dumazet <edumazet@google.com>
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| 5.4 | Success | Success |
next prev parent reply other threads:[~2025-07-18 1:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 12:45 [PATCH 5.4.y 0/6] Backport few sch_sfq fixes Harshit Mogalapalli
2025-07-17 12:45 ` [PATCH 5.4.y 1/6] net_sched: sch_sfq: annotate data-races around q->perturb_period Harshit Mogalapalli
2025-07-18 1:34 ` Sasha Levin
2025-07-17 12:45 ` [PATCH 5.4.y 2/6] net_sched: sch_sfq: handle bigger packets Harshit Mogalapalli
2025-07-18 1:34 ` Sasha Levin [this message]
2025-07-17 12:45 ` [PATCH 5.4.y 3/6] net_sched: sch_sfq: don't allow 1 packet limit Harshit Mogalapalli
2025-07-18 1:34 ` Sasha Levin
2025-07-17 12:45 ` [PATCH 5.4.y 4/6] net_sched: sch_sfq: use a temporary work area for validating configuration Harshit Mogalapalli
2025-07-18 1:34 ` Sasha Levin
2025-07-17 12:45 ` [PATCH 5.4.y 5/6] net_sched: sch_sfq: move the limit validation Harshit Mogalapalli
2025-07-18 1:34 ` Sasha Levin
2025-07-17 12:45 ` [PATCH 5.4.y 6/6] net_sched: sch_sfq: reject invalid perturb period Harshit Mogalapalli
2025-07-18 1:34 ` 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=1752797234-97c617e8@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;
as well as URLs for NNTP newsgroup(s).