All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: wfg@linux.intel.com
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: automated warning notifications
Date: Thu, 14 Jun 2012 17:25:23 +0000	[thread overview]
Message-ID: <20120614172523.GB4400@mwanda> (raw)

Hi Fengguang,

I also check new static checker warnings and sometimes email people.
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)

Quite often those messages are false positive and the value is
truncated deliberately.  In this case it looks suspicious and I
would maybe email about it.  If I knew what kind of messages you
check and which you ignore that would help me.

Perhaps there is an email list I could subscribe to to see if you
had already sent a message.

regards,
dan carpenter

WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: wfg@linux.intel.com
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: automated warning notifications
Date: Thu, 14 Jun 2012 20:25:23 +0300	[thread overview]
Message-ID: <20120614172523.GB4400@mwanda> (raw)

Hi Fengguang,

I also check new static checker warnings and sometimes email people.
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)

Quite often those messages are false positive and the value is
truncated deliberately.  In this case it looks suspicious and I
would maybe email about it.  If I knew what kind of messages you
check and which you ignore that would help me.

Perhaps there is an email list I could subscribe to to see if you
had already sent a message.

regards,
dan carpenter

             reply	other threads:[~2012-06-14 17:25 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14 17:25 Dan Carpenter [this message]
2012-06-14 17:25 ` automated warning notifications Dan Carpenter
2012-06-15  1:48 ` Fengguang Wu
2012-06-15  1:48   ` Fengguang Wu
2012-06-15  7:12   ` Dan Carpenter
2012-06-15  7:12     ` Dan Carpenter
2012-06-15  7:58     ` Fengguang Wu
2012-06-15  7:58       ` Fengguang Wu
2012-06-15  8:31       ` Josh Triplett
2012-06-15  8:31         ` Josh Triplett
2012-06-15  8:54         ` Fengguang Wu
2012-06-15  8:54           ` Fengguang Wu
2012-06-15 16:48           ` Randy Dunlap
2012-06-15 16:48             ` Randy Dunlap
2012-06-16  9:17             ` Fengguang Wu
2012-06-16  9:17               ` Fengguang Wu
2012-06-16 17:44               ` Randy Dunlap
2012-06-16 17:44                 ` Randy Dunlap
2012-06-15 10:40       ` Julia Lawall
2012-06-15 10:40         ` Julia Lawall
2012-06-15 11:19         ` Dan Carpenter
2012-06-15 11:19           ` Dan Carpenter
2012-06-15 13:33           ` Peter Senna Tschudin
2012-06-15 13:33             ` Peter Senna Tschudin
2012-06-15 13:53             ` Dan Carpenter
2012-06-15 13:53               ` Dan Carpenter
2012-06-15 15:49               ` Peter Senna Tschudin
2012-06-15 15:49                 ` Peter Senna Tschudin
2012-06-15 14:34           ` Fengguang Wu
2012-06-15 14:34             ` Fengguang Wu
2012-06-16  7:50             ` Cong Wang
2012-06-16  7:50               ` Cong Wang
2012-06-16  9:01               ` Fengguang Wu
2012-06-16  9:01                 ` Fengguang Wu
2012-07-02 12:45   ` Dan Carpenter
2012-07-02 12:45     ` Dan Carpenter
2012-07-06  3:07 ` Fengguang Wu
2012-07-06  3:07   ` Fengguang Wu

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=20120614172523.GB4400@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wfg@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.