From: Krystian Kaniewski <krystianmkaniewski@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Vinicius Costa Gomes <vinicius.gomes@intel.com>,
Jamal Hadi Salim <jhs@mojatatu.com>,
Jiri Pirko <jiri@resnulli.us>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 0/2] net/sched: taprio: fix RCU stall from replayed schedule entries
Date: Fri, 9 Oct 2026 11:42:49 +0200 [thread overview]
Message-ID: <6d9c9501-70d0-4e1e-933c-eb5a45bef97a@gmail.com> (raw)
In-Reply-To: <20261008091732.7794253a@kernel.org>
On 10/8/26 18:17, Jakub Kicinski wrote:
> Could you restructure the helper to avoid reading `entry` after the loop,
Thanks for the review. I will prepare a v2 that fixes this. While
reviewing the patch again locally I also found a few lines over the
80 column limit, and v2 will fix those as well.
--
Krystian Kaniewski
prev parent reply other threads:[~2026-10-09 9:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 11:33 [PATCH net 0/2] net/sched: taprio: fix RCU stall from replayed schedule entries Krystian Kaniewski
2026-10-06 11:33 ` [PATCH net 1/2] net/sched: taprio: reject software schedules that overflow their timestamps Krystian Kaniewski
2026-10-06 11:33 ` [PATCH net 2/2] net/sched: taprio: do not replay missed entries in advance_sched() Krystian Kaniewski
2026-10-08 16:17 ` [PATCH net 0/2] net/sched: taprio: fix RCU stall from replayed schedule entries Jakub Kicinski
2026-10-09 9:42 ` Krystian Kaniewski [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=6d9c9501-70d0-4e1e-933c-eb5a45bef97a@gmail.com \
--to=krystianmkaniewski@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vinicius.gomes@intel.com \
--cc=vladimir.oltean@nxp.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.