All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roman Gushchin <roman.gushchin@linux.dev>
To: Alison Schofield <alison.schofield@intel.com>
Cc: 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, 03 Oct 2026 20:10:37 +0000	[thread overview]
Message-ID: <7ia4jynyzgsi.fsf@castle.c.googlers.com> (raw)
In-Reply-To: <asA_b1s4iVx2_v-U@aschofie-mobl2.lan> (Alison Schofield's message of "Fri, 2 Oct 2026 16:34:07 -0700")

Alison Schofield <alison.schofield@intel.com> writes:

> On Thu, Sep 17, 2026 at 11:30:23PM +0000, Roman Gushchin 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.
>
> Hi Roman,
>
> The access is not working for me for my linux-cxl and nvdimm.
> I ask it to send the email link and nothing happens.
>
> Anything else needed here?
>

Hi Alison,

not really. There was a temporary outage with the email delivery,
which I'm about to fix. Please, try again.

Thanks

  reply	other threads:[~2026-10-03 20:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-17 23:30 sashiko & pre-existing bugs Roman Gushchin
2026-09-18  4:25 ` Kees Cook
2026-10-02 23:34 ` Alison Schofield
2026-10-03 20:10   ` Roman Gushchin [this message]
2026-10-03 17:24 ` SJ Park
2026-10-03 18:09   ` SJ Park

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=7ia4jynyzgsi.fsf@castle.c.googlers.com \
    --to=roman.gushchin@linux.dev \
    --cc=alison.schofield@intel.com \
    --cc=jgg@nvidia.com \
    --cc=kees@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mason@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.