From: Mark Brown <broonie@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: ksummit-discuss@lists.linux-foundation.org
Subject: Re: [Ksummit-discuss] Kernel Summit Agenda -- 2nd draft
Date: Wed, 21 Oct 2015 17:09:07 +0100 [thread overview]
Message-ID: <20151021160907.GM32054@sirena.org.uk> (raw)
In-Reply-To: <5627AD56.7050500@roeck-us.net>
[-- Attachment #1: Type: text/plain, Size: 964 bytes --]
On Wed, Oct 21, 2015 at 08:20:54AM -0700, Guenter Roeck wrote:
> Number of build and runtime breakages in -next is a bit high, and fixes are
> sometimes slow to roll in. At least in part this is because those responsible
> for breakages are not informed, but I have also seen problems which were
> known for weeks to propagate into mainline before they got fixed, even if
> the culprit was informed. This could use some improvement, though I am not
> really sure how we could get there. Make more noise ?
Noise is probably a large part of it, having a human following up about
issues seems to help a lot.
I've seen some active resistance to pushing fixes to mainline without
lengthy soaks in -next in a very rules based fashion which isn't super
awesome when it takes out other testing due to the breakage. As the
test coverage improves this is going to be getting to be more and more
of an issue as failures to build or boot will cause gaps in other
testing.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-10-21 16:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 22:03 Theodore Ts'o
2015-10-20 23:17 ` Jason Cooper
2015-10-21 2:36 ` Olof Johansson
2015-10-21 14:56 ` Theodore Ts'o
2015-10-21 15:20 ` Guenter Roeck
2015-10-21 16:09 ` Mark Brown [this message]
2015-10-21 16:37 ` Guenter Roeck
2015-10-21 17:24 ` Luck, Tony
2015-10-21 18:53 ` Jonathan Corbet
2015-10-21 17:25 ` Mark Brown
2015-10-22 15:25 ` Theodore Ts'o
2015-10-22 20:01 ` Alexandre Belloni
2015-10-24 15:19 ` Rafael J. Wysocki
2015-10-26 5:56 ` Luis R. Rodriguez
2015-10-26 6:12 ` Eric W. Biederman
2015-10-26 6:28 ` Josh Triplett
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=20151021160907.GM32054@sirena.org.uk \
--to=broonie@kernel.org \
--cc=ksummit-discuss@lists.linux-foundation.org \
--cc=linux@roeck-us.net \
/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