From: SJ Park <sj@kernel.org>
To: SJ Park <sj@kernel.org>
Cc: Roman Gushchin <roman.gushchin@linux.dev>,
sashiko <sashiko@lists.linux.dev>,
LKML <linux-kernel@vger.kernel.org>,
Chris Mason <mason@kernel.org>, Kees Cook <kees@kernel.org>,
Jason Gunthorpe <jgg@nvidia.com>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: sashiko & pre-existing bugs
Date: Sat, 3 Oct 2026 11:09:41 -0700 [thread overview]
Message-ID: <20261003180941.35452-1-sj@kernel.org> (raw)
In-Reply-To: <20261003172449.33985-1-sj@kernel.org>
On Sat, 3 Oct 2026 10:24:49 -0700 SJ Park <sj@kernel.org> wrote:
> Hello Roman and Sashiko team,
>
> On Thu, 17 Sep 2026 23:30:23 +0000 Roman Gushchin <roman.gushchin@linux.dev> wrote:
>
> > Hello,
> >
> > as some of you might notice, a couple of days ago sashiko stopped to
> > report preexisting bugs together with not-yet-introduced new issues.
> > Instead, it started putting them into the database. All M: and R: in the
> > current MAINTAINERS file have full access to corresponding bugs.
> >
> > There is a new "Bugs" button in the top right corner which is the access
> > to the database. You don't need to create an account, invent a password,
> > etc. It's all stateless.
>
> I asked it to send the sign-in link for sj@kernel.org. But I don't receive the
> link. I waited more than 10 minutes and checked spam folder, but nothing is
> found. The last time I tried to sign in was a couple of weeks ago, and it
> worked at that time. I wonder if this is also related with my previously
> reported issue [1].
Maybe it was a temporal issue, or something is just fixed. I tried sign-in
again, and this time I was able to get the sign-in link within a minute.
>
> Could you please take a look when you get a chance?
So, please ignore the above request.
>
> [1] https://lore.kernel.org/20261003171045.33520-1-sj@kernel.org
Thank you again for making Sashiko always great!
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-10-03 18:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 23:30 Roman Gushchin
2026-09-18 4:25 ` Kees Cook
2026-10-02 23:34 ` Alison Schofield
2026-10-03 20:10 ` Roman Gushchin
2026-10-03 17:24 ` SJ Park
2026-10-03 18:09 ` SJ Park [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=20261003180941.35452-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=jgg@nvidia.com \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@kernel.org \
--cc=roman.gushchin@linux.dev \
--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
all inboxes | Powered by JetHome®