From: Mark Brown <broonie@kernel.org>
To: Sasha Levin <sashal@kernel.org>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] stable kernel process automation and improvement
Date: Fri, 5 Jul 2019 17:41:42 +0100 [thread overview]
Message-ID: <20190705164142.GC20625@sirena.org.uk> (raw)
In-Reply-To: <20190703013557.GQ11506@sasha-vm>
[-- Attachment #1: Type: text/plain, Size: 510 bytes --]
On Tue, Jul 02, 2019 at 09:35:57PM -0400, Sasha Levin wrote:
> - Concerns about how well -stable kernels are tested.
> - "Fixes for fixes" end up being missed.
> - Saner AUTOSEL process.
I'm a bit worried about these, especially pushed together - one
of the things the AUTOSEL stuff does quite often is pull in
driver changes and our coverage of drivers is especially weak.
When a person has explicitly flagged something for stable it's a
still risky but the automation adds that extra level of
uncertainty.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-07-05 17:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 1:35 Sasha Levin
2019-07-03 14:57 ` Laura Abbott
2019-07-05 13:54 ` Michael Ellerman
2019-07-05 14:13 ` Takashi Iwai
2019-07-05 16:17 ` Greg KH
2019-07-05 16:52 ` Sasha Levin
2019-07-05 16:41 ` Mark Brown [this message]
2019-07-05 20:12 ` Sasha Levin
2019-07-06 0:32 ` Mark Brown
2019-07-08 11:02 ` Sasha Levin
2019-07-08 11:35 ` Jiri Kosina
2019-07-08 12:34 ` Greg KH
2019-07-08 17:56 ` Sasha Levin
2019-07-08 12:37 ` Mark Brown
2019-07-08 14:05 ` Guenter Roeck
2019-07-08 14:33 ` Takashi Iwai
2019-07-08 15:10 ` Greg KH
2019-07-08 15:18 ` Takashi Iwai
2019-07-08 18:08 ` Sasha Levin
2019-07-08 21:31 ` Jiri Kosina
2019-07-09 15:44 ` Rafael J. Wysocki
2019-07-09 21:05 ` Takashi Iwai
2019-07-09 15:21 ` Laura Abbott
2019-07-08 14:50 ` Mark Brown
2019-07-08 15:06 ` Greg KH
2019-07-08 15:27 ` Mark Brown
2019-07-08 18:01 ` Sasha Levin
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=20190705164142.GC20625@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