public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
	Randy Dunlap <rdunlap@xenotime.net>
Subject: Re: automated warning notifications
Date: Fri, 06 Jul 2012 03:07:01 +0000	[thread overview]
Message-ID: <20120706030701.GB6848@localhost> (raw)
In-Reply-To: <20120615014835.GA5695@localhost>
In-Reply-To: <20120614172523.GB4400@mwanda>

> On Fri, Jun 15, 2012 at 09:48:35AM +0800, Fengguang Wu wrote:
> > Hi Dan,
> > 
> > On Thu, Jun 14, 2012 at 08:25:23PM +0300, Dan Carpenter wrote:
> > > Hi Fengguang,
> > > 
> > > I also check new static checker warnings and sometimes email people.
> > 
> > That would be nice!
> > 
> > > I wonder if we are duplicating each others work.  For example, did
> > > you send an email asking about the following Sparse warning:
> > > 
> > > sound/soc/codecs/ab8500-codec.c:1959:53: warning: cast truncates bits from constant value (1013 becomes 13)
> > 
> > I did try sending out sparse warnings to people, some time ago...
> 
> Apparently you have started up again?  We're starting to trod on
> each other's toes and people are getting annoyed with me because I
> am reporting them after you...  :/

Sorry for that!  Yeah I restarted the sparse checks and have been
sending out private emails after basic sanity check. Although there
are 10000 existing sparse warnings, there are only very few *new*
sparse warnings per day. This is pretty acceptable.

> Randy has suggested that we send these automated messages to
> kernel-janitors.  I don't know how the other people on kernel
> janitors feel about this but I would be fine with it.

Randy also suggested kernel-janitors. So let's try it. I'll CC
kernel-janitors for all of my error/warning reports and let's check
how well it works.

Thanks,
Fengguang

      parent reply	other threads:[~2012-07-06  3:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14 17:25 automated warning notifications Dan Carpenter
2012-06-15  1:48 ` Fengguang Wu
2012-06-15  7:12   ` Dan Carpenter
2012-06-15  7:58     ` Fengguang Wu
2012-06-15  8:31       ` Josh Triplett
2012-06-15  8:54         ` Fengguang Wu
2012-06-15 16:48           ` Randy Dunlap
2012-06-16  9:17             ` Fengguang Wu
2012-06-16 17:44               ` Randy Dunlap
2012-06-15 10:40       ` Julia Lawall
2012-06-15 11:19         ` Dan Carpenter
2012-06-15 13:33           ` Peter Senna Tschudin
2012-06-15 13:53             ` Dan Carpenter
2012-06-15 15:49               ` Peter Senna Tschudin
2012-06-15 14:34           ` Fengguang Wu
2012-06-16  7:50             ` Cong Wang
2012-06-16  9:01               ` Fengguang Wu
2012-07-02 12:45   ` Dan Carpenter
2012-07-06  3:07 ` Fengguang Wu [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=20120706030701.GB6848@localhost \
    --to=fengguang.wu@intel.com \
    --cc=dan.carpenter@oracle.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.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