From: Mark Brown <broonie@kernel.org>
To: Sasha Levin <sashal@kernel.org>
Cc: ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Squashing bugs!
Date: Mon, 3 Jun 2019 23:11:31 +0100 [thread overview]
Message-ID: <20190603221131.GE2456@sirena.org.uk> (raw)
In-Reply-To: <20190603211004.GU12898@sasha-vm>
[-- Attachment #1: Type: text/plain, Size: 1382 bytes --]
On Mon, Jun 03, 2019 at 05:10:04PM -0400, Sasha Levin wrote:
> Would it make sense to do some bikeshedding around how an ideal email
> bug report should look like, and then get syzbot and maybe kernelci to
> switch to using this new format as an experiment?
> A bunch the syzbot/kernelci/etc folks will be at LPC as well, and we'll
> have the testing & fuzzing MC going on where this can be discussed and
> agreed on once there is a concrete proposal.
I think we'll find that there's a lot of variation in what's useful to
report directly in the e-mail and how comes from the particular tests
that are being done, what's critical information about the environment
will vary quite a bit and there's going to be taste differences as well.
A lot of this is a combination of common sense and the reporters being
able to be responsive to feedback from their users, there's not much
commonality in the formatting of the existing reports from static
analysis but they're pretty much all useful (at least the ones I tend to
get are useful to me).
There is the question of tooling to track the bugs between multiple bots
which would benefit if they were doing standard things but if people are
working on that rather than trying to serve both humans and computers at
once we might be better off with some sort of API and providing a URL in
the emails for the machines to go and look at.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-06-03 22:11 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 23:30 Shuah Khan
2019-05-31 12:01 ` Laura Abbott
2019-05-31 15:56 ` Shuah Khan
2019-06-03 5:01 ` Leon Romanovsky
2019-05-31 22:15 ` Kees Cook
2019-06-03 10:42 ` Jan Kara
2019-06-04 18:29 ` Laura Abbott
2019-06-03 16:48 ` Shuah Khan
2019-06-02 18:09 ` Sasha Levin
2019-06-03 17:25 ` Shuah Khan
2019-06-03 18:09 ` Konstantin Ryabitsev
2019-06-03 19:32 ` Shuah Khan
2019-06-03 20:48 ` Linus Torvalds
2019-06-03 21:10 ` Sasha Levin
2019-06-03 21:15 ` Jiri Kosina
2019-06-03 21:23 ` Linus Torvalds
2019-06-03 21:28 ` Jiri Kosina
2019-06-03 22:11 ` Mark Brown [this message]
2019-06-04 17:16 ` Shuah Khan
2019-06-05 9:27 ` Mark Brown
2019-06-05 11:48 ` Geert Uytterhoeven
2019-06-05 18:16 ` Shuah Khan
2019-06-05 13:19 ` Sasha Levin
2019-06-05 19:05 ` Shuah Khan
2019-06-04 18:09 ` Laura Abbott
2019-06-05 12:49 ` Sasha Levin
2019-06-04 21:43 ` Konstantin Ryabitsev
2019-06-04 22:02 ` Shuah Khan
2019-06-04 22:22 ` Konstantin Ryabitsev
2019-06-05 17:54 ` Shuah Khan
2019-06-03 20:59 ` Sasha Levin
-- strict thread matches above, loose matches on Subject: below --
2019-05-29 22:34 Shuah Khan
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=20190603221131.GE2456@sirena.org.uk \
--to=broonie@kernel.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=sashal@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