From: Mark Brown <broonie@kernel.org>
To: Valentin Rothberg <valentinrothberg@gmail.com>
Cc: Paul Bolle <pebolle@tiscali.nl>,
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 14:07:59 +0100 [thread overview]
Message-ID: <20150522130759.GZ21391@sirena.org.uk> (raw)
In-Reply-To: <CAD3Xx4LAO_O1CjoUz5XseRB=JHzyM16i7zLAqLEYgoi1a7_8bg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 932 bytes --]
On Fri, May 22, 2015 at 12:53:16PM +0200, Valentin Rothberg wrote:
> > One effect of being too keen to report things is that a high false
> > positive rate will cause people to pay less attention, if the source is
> > usually just generating noise then it gets tuned out.
> Note, that we keep a list of all reported items. If we know (for
> certain) that something will be applied, we won't report anything
> similar for a longer period of time.
> I don't want those reports to be seen as spam, so I guess we need to
> find a less noisy approach. It's something I do as a hobby besides my
> PhD, so the only intention is to help, not to annoy people.
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. Doing
it immediately is likely to generate lots of false positives simply
because coordinating down to a single day is a lot of effort.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-05-22 13:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 8:20 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 [this message]
2015-05-22 14:03 ` Paul Bolle
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=20150522130759.GZ21391@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andreas.ruprecht@fau.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--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
all inboxes | Powered by JetHome®