Linux real-time development
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Haoran Wang <haoranwangsec@gmail.com>
Cc: David Laight <david.laight.linux@gmail.com>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-rt-devel@lists.linux.dev, andrew+netdev@lunn.ch,
	davem@davemloft.net, edumazet@kernel.org, pabeni@redhat.com,
	rostedt@goodmis.org
Subject: Re: [PATCH v4] libcxgb: use raw_cpu_ptr() in ppm_get_cpu_entries()
Date: Wed, 18 Nov 2026 17:15:21 -0800	[thread overview]
Message-ID: <20261118171521.18beb1e9@kernel.org> (raw)
In-Reply-To: <179430137148.488859.15630804371226096686@kernel.org>

On Tue, 10 Nov 2026 09:02:51 +0000 netdev-bot+sinfo@kernel.org wrote:
> This is an automated message. This series looks like a fix, but its
> commit messages seem to be missing some information:
> 
>  - How the issue was discovered, e.g. hit in production, hit during
>    development, syzbot report, manual code inspection, LLM or static
>    analysis tool scan.
> 
>  - Whether the issue was actually triggered, or is only theoretical
>    (e.g. found by code inspection). If it was triggered please include
>    the symptoms, like the stack trace or error messages.

If / when you post v5 please answer these questions in the commit msg.

Please *do not* submit v5 in the same thread/in-reply to previous
posting, start a new thread.

  reply	other threads:[~2026-11-19  1:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19 13:22 [PATCH] libcxgb: use raw_cpu_ptr() in ppm_get_cpu_entries() Haoran Wang
2026-10-19 13:29 ` netdev-bot+sinfo
2026-10-19 13:29 ` Sebastian Andrzej Siewior
2026-10-20 13:22 ` sashiko-bot
2026-10-22  7:25 ` netdev-bot+sashiko
     [not found] ` <CANZ3JQQrrntu0TefPZC79pKSmsOfwAngRJyuaVm81DYaJNFHFQ@mail.gmail.com>
2026-11-09 10:07   ` [PATCH v3] " Haoran Wang
2026-11-09 10:11     ` netdev-bot+sinfo
2026-11-09 20:03     ` David Laight
2026-11-10  8:57       ` [PATCH v4] " Haoran Wang
2026-11-10  9:02         ` netdev-bot+sinfo
2026-11-19  1:15           ` Jakub Kicinski [this message]
2026-11-11  8:58         ` sashiko-bot
2026-11-11 12:17         ` Sebastian Andrzej Siewior
2026-11-12  2:59         ` netdev-bot+sashiko
2026-11-10 10:08     ` [PATCH v3] " sashiko-bot
2026-11-11 16:08     ` netdev-bot+sashiko

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=20261118171521.18beb1e9@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=bigeasy@linutronix.de \
    --cc=davem@davemloft.net \
    --cc=david.laight.linux@gmail.com \
    --cc=edumazet@kernel.org \
    --cc=haoranwangsec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-devel@lists.linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rostedt@goodmis.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