From: Jakub Kicinski <kuba@kernel.org>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: Simon Horman <horms@kernel.org>,
netdev@vger.kernel.org, victor@mojatatu.com, jiri@resnulli.us,
davem@davemloft.net, edumazet@kernel.org, pabeni@redhat.com,
stable@vger.kernel.org, sashiko-bot@kernel.org
Subject: Re: [PATCH net 2/2 repost2] net/sched: sch_teql: keep skb->dev consistent on the arp-queue path
Date: Mon, 26 Oct 2026 17:46:43 -0700 [thread overview]
Message-ID: <20261026174643.088e3f49@kernel.org> (raw)
In-Reply-To: <CAM0EoMm9piw8gLJ=t9YYNu2-8zb=qfA3G6djchL0QaeZZvaNfA@mail.gmail.com>
On Mon, 26 Oct 2026 19:51:33 -0400 Jamal Hadi Salim wrote:
> > This is an AI-generated review of your patch. The human sending this
> > email says "Hi Jamal, passing this on for your consideration as it
> > seems to have got stuck somewhere."
>
> There was nothing wrong with the headers this time - so not sure what
> is going on. A bit frustrating.
It is frustrating, you are the only one with these issues.
Patch 2 is posted in reply to patch 1. IDK what else is wrong.
> In any case these are complaints about commit messages in both 1/2 and
> this i.e there is nothing to change in the code.
> If necessary, I can resend repost 3 with the fixed commit clarifying
> the "identity for every other parker"
next prev parent reply other threads:[~2026-10-27 0:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 10:38 [PATCH net 0/2 repost2] net/sched: sch_teql: fix shared headroom and header strip Jamal Hadi Salim
2026-10-20 10:38 ` [PATCH net 1/2 repost2] net/sched: sch_teql: fix shared headroom and header strip on slave retry Jamal Hadi Salim
2026-10-20 10:38 ` [PATCH net 2/2 repost2] net/sched: sch_teql: keep skb->dev consistent on the arp-queue path Jamal Hadi Salim
2026-10-26 16:07 ` Simon Horman
2026-10-26 23:51 ` Jamal Hadi Salim
2026-10-27 0:46 ` Jakub Kicinski [this message]
2026-10-27 7:25 ` Jamal Hadi Salim
2026-10-27 7:44 ` Jamal Hadi Salim
2026-10-27 8:04 ` Jamal Hadi Salim
2026-10-27 18:29 ` Simon Horman
2026-10-27 19:45 ` Jamal Hadi Salim
2026-10-27 21:03 ` Jamal Hadi Salim
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=20261026174643.088e3f49@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sashiko-bot@kernel.org \
--cc=stable@vger.kernel.org \
--cc=victor@mojatatu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox