public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Mark Brown <broonie@kernel.org>
Cc: Valentin Rothberg <valentinrothberg@gmail.com>,
	stwiss.opensource@diasemi.com, lgirdwood@gmail.com,
	support.opensource@diasemi.com, linux-kernel@vger.kernel.org,
	Andreas Ruprecht <andreas.ruprecht@fau.de>,
	hengelein Stefan <stefan.hengelein@fau.de>
Subject: Re: regulator: da9062: undefined Kconfig option MFD_DA9062
Date: Fri, 22 May 2015 16:03:42 +0200	[thread overview]
Message-ID: <1432303422.27695.130.camel@x220> (raw)
In-Reply-To: <20150522130759.GZ21391@sirena.org.uk>

On Fri, 2015-05-22 at 14:07 +0100, Mark Brown wrote:
> I'd expect that holding off on the initial report for a while (at least
> a week but I'd guess longer) would probably avoid a lot of noise.

I have data on roughly a year worth of linux-next and mainline releases.
I might try to see if I can extract from it things like:
- how often this (ie, pre merged drivers) happens;
- how long it takes for those issue to disappear; and
- what made these issue disappear (that might be hard, because it
  probably requires cross checking my (incomplete) mail archive.)

This will take quite some time, I'm afraid. Provided it actually works,
that is.

> Doing
> it immediately is likely to generate lots of false positives simply
> because coordinating down to a single day is a lot of effort.

False positives is a bit ambiguous here. I don't think we often, if
ever, sent out notifications that were flat out wrong. But yes, some
issues can be expected to get resolved given a bit of time. The hard
part is knowing beforehand which issues will be resolved quickly and
which won't.

Thanks,


Paul Bolle


      reply	other threads:[~2015-05-22 14:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-22  8:20 regulator: da9062: undefined Kconfig option MFD_DA9062 Valentin Rothberg
2015-05-22  8:57 ` Opensource [Steve Twiss]
2015-05-26 10:37   ` Lee Jones
2015-05-27  7:19     ` Opensource [Steve Twiss]
2015-05-22  9:35 ` Mark Brown
2015-05-22  9:52   ` Paul Bolle
2015-05-22 10:12     ` Mark Brown
2015-05-22 10:53       ` Valentin Rothberg
2015-05-22 13:07         ` Mark Brown
2015-05-22 14:03           ` Paul Bolle [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=1432303422.27695.130.camel@x220 \
    --to=pebolle@tiscali.nl \
    --cc=andreas.ruprecht@fau.de \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefan.hengelein@fau.de \
    --cc=stwiss.opensource@diasemi.com \
    --cc=support.opensource@diasemi.com \
    --cc=valentinrothberg@gmail.com \
    /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