ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] stable kernel process automation and improvement
Date: Mon, 8 Jul 2019 15:50:45 +0100	[thread overview]
Message-ID: <20190708145045.GC12731@sirena.co.uk> (raw)
In-Reply-To: <102219fd-4ba0-e1ff-b2e3-9a0a43392c4c@roeck-us.net>

[-- Attachment #1: Type: text/plain, Size: 858 bytes --]

On Mon, Jul 08, 2019 at 07:05:44AM -0700, Guenter Roeck wrote:
> On 7/8/19 5:37 AM, Mark Brown wrote:

> > I'm not sure how many people will actually report problems they
> > experience upstream rather than just fixing things locally and
> > just moving on.  The more code is the more likely it is that one
> > of the users will report things.

> I for my part will most definitely report any such problems, since each
> regression in stable releases is used as argument against merging
> stable releases (even if the regression rate is negligible), and I am
> very interested in getting that regression rate as close to zero as
> possible. Reporting each and every regression is an essential part
> of that.

Me too - but I'm pretty sure for example most of the product
teams I've worked with at consumer electronics companies would
never even consider it.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2019-07-08 14:50 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
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 [this message]
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=20190708145045.GC12731@sirena.co.uk \
    --to=broonie@kernel.org \
    --cc=ksummit-discuss@lists.linuxfoundation.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