From: Lukas Wunner <lukas@wunner.de>
To: sashiko@lists.linux.dev
Cc: alistair23@gmail.com, ojeda@kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH 02/18] X.509: Make certificate parser public
Date: Thu, 14 May 2026 09:22:56 +0200 [thread overview]
Message-ID: <agV4ULnj0Y1UV1Xi@wunner.de> (raw)
In-Reply-To: <20260508034543.D9D2FC2BCB0@smtp.kernel.org>
On Fri, May 08, 2026 at 03:45:43AM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] The commit message claims to adjust the `#include <linux/time.h>` directive to `#include <linux/time64.h>`, but the patch fails to do so.
Observation is valid, but appears to be caused by an outdated commit
on Alistair's development branch. The corresponding commit on my
development branch does change the #include directive as advertised
in the commit message:
https://github.com/l1k/linux/commit/64b5f6e24ba9
parent reply other threads:[~2026-05-14 7:22 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20260508034543.D9D2FC2BCB0@smtp.kernel.org>]
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=agV4ULnj0Y1UV1Xi@wunner.de \
--to=lukas@wunner.de \
--cc=alistair23@gmail.com \
--cc=linux-pci@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=sashiko@lists.linux.dev \
/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