From: Davidlohr Bueso <dave@stgolabs.net>
To: netdev-bot+sinfo@kernel.org
Cc: jk@codeconstruct.com.au, matt@codeconstruct.com.au,
kuba@kernel.org, pabeni@redhat.com, anisa.su@samsung.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mctp: accept MSG_CMSG_COMPAT in recvmsg
Date: Sun, 1 Nov 2026 12:41:32 -0800 [thread overview]
Message-ID: <20261101204132.eifrbvmpjjktdkno@offworld> (raw)
In-Reply-To: <179356374166.3286.2383588037768263377@kernel.org>
On Sun, 01 Nov 2026, netdev-bot+sinfo@kernel.org wrote:
>Hi!
>
>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.
>
>Please do not repost the series just to address the above. Instead,
>reply to this email with the missing information, so that reviewers
>can take it into account. If the series needs another revision for
>other reasons, please include the information in the commit messages
>then.
This is not a random fix, I actually ran into this while testing 32-bit
support for libcxlmi: https://github.com/computexpresslink/libcxlmi/pull/62
>
>The evaluation is done by an LLM so it may be wrong, if you think
>that is the case please reply and explain.
next prev parent reply other threads:[~2026-11-01 20:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-01 20:03 Davidlohr Bueso
2026-11-01 20:09 ` netdev-bot+sinfo
2026-11-01 20:41 ` Davidlohr Bueso [this message]
2026-11-05 13:58 ` Simon Horman
2026-11-05 15:32 ` Davidlohr Bueso
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=20261101204132.eifrbvmpjjktdkno@offworld \
--to=dave@stgolabs.net \
--cc=anisa.su@samsung.com \
--cc=jk@codeconstruct.com.au \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=netdev-bot+sinfo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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
all inboxes | Powered by JetHome®