public inbox for linux-kselftest@vger.kernel.org
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Roman Gushchin <roman.gushchin@linux.dev>, Shuah <shuah@kernel.org>
Cc: linux-kselftest@vger.kernel.org, sashiko@lists.linux.dev,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: Sashiko.dev for kselftest
Date: Wed, 1 Apr 2026 17:35:49 -0600	[thread overview]
Message-ID: <8290d427-ae1f-4e90-b988-c209e81ec85c@linuxfoundation.org> (raw)
In-Reply-To: <877bqqh11y.fsf@linux.dev>

On 4/1/26 14:34, Roman Gushchin wrote:
> Shuah <shuah@kernel.org> writes:
> 
> Hi Shuah,
> 
> Sure, will add later today.
> 
>> Hi Roman,
>>
>> Please add linux-kselftest list to sashiko.dev for reviews.
>>
>> There might be double coverage for patches cc'ed to lkml
>> and other lists such as mm, net, bpf etc. Hope that won't
>> cause problems.
> 
> It's not a problem at all.
> 
> What I believe might be a problem: kselftests are mostly userspace
> code and at least some parts are written somewhat loosely (which
> is totally fine for tests), so Sashiko will report a ton of issues,
> many of them are not worth fixing.

Good point. Maybe we can also find things that are worth fixing. It will
be an experiment.

> 
> So I guess it will be good to put down a kselftest-specific prompt with
> some guidance what we believe is acceptable in tests code and what's not.
> 

I can definitely do that depending on what we find.

thanks,
-- Shuah

      reply	other threads:[~2026-04-01 23:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-01 19:51 Sashiko.dev for kselftest Shuah
2026-04-01 20:34 ` Roman Gushchin
2026-04-01 23:35   ` Shuah Khan [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=8290d427-ae1f-4e90-b988-c209e81ec85c@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=roman.gushchin@linux.dev \
    --cc=sashiko@lists.linux.dev \
    --cc=shuah@kernel.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