From: Markus Elfring <Markus.Elfring@web.de>
To: Enrico Weigelt <lkml@metux.net>, kernel-janitors@vger.kernel.org
Cc: Michal Marek <michal.lkml@markovi.net>,
Nicolas Palix <nicolas.palix@imag.fr>,
LKML <linux-kernel@vger.kernel.org>,
Ding Xiang <dingxiang@cmss.chinamobile.com>,
Coccinelle <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] [v2] Coccinelle: Suppression of warnings?
Date: Mon, 1 Jul 2019 14:40:43 +0200 [thread overview]
Message-ID: <eb95005d-e685-0a8f-416c-1a30ad3fbaa0@web.de> (raw)
In-Reply-To: <0b48a5c5-0814-6414-39ba-beb1b8b5253a@metux.net>
> By the way: do we have any mechanism for explicitly suppressing
> individual warnings (some kind of annotation),
I do not know such an accepted specification interface
(for the handling together with SmPL scripts) so far.
How would you identify possibly unwanted messages in a safe way?
> when the maintainer is sure that some particular case is a false-positive ?
Do you know any specific source code places already where you would get
concerned about the confidence and relevance of the provided information?
Regards,
Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
WARNING: multiple messages have this Message-ID (diff)
From: Markus Elfring <Markus.Elfring@web.de>
To: Enrico Weigelt <lkml@metux.net>, kernel-janitors@vger.kernel.org
Cc: Michal Marek <michal.lkml@markovi.net>,
Nicolas Palix <nicolas.palix@imag.fr>,
LKML <linux-kernel@vger.kernel.org>,
Ding Xiang <dingxiang@cmss.chinamobile.com>,
Coccinelle <cocci@systeme.lip6.fr>
Subject: Re: [v2] Coccinelle: Suppression of warnings?
Date: Mon, 01 Jul 2019 12:40:43 +0000 [thread overview]
Message-ID: <eb95005d-e685-0a8f-416c-1a30ad3fbaa0@web.de> (raw)
In-Reply-To: <0b48a5c5-0814-6414-39ba-beb1b8b5253a@metux.net>
> By the way: do we have any mechanism for explicitly suppressing
> individual warnings (some kind of annotation),
I do not know such an accepted specification interface
(for the handling together with SmPL scripts) so far.
How would you identify possibly unwanted messages in a safe way?
> when the maintainer is sure that some particular case is a false-positive ?
Do you know any specific source code places already where you would get
concerned about the confidence and relevance of the provided information?
Regards,
Markus
WARNING: multiple messages have this Message-ID (diff)
From: Markus Elfring <Markus.Elfring@web.de>
To: Enrico Weigelt <lkml@metux.net>, kernel-janitors@vger.kernel.org
Cc: Gilles Muller <Gilles.Muller@lip6.fr>,
Julia Lawall <Julia.Lawall@lip6.fr>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Michal Marek <michal.lkml@markovi.net>,
Nicolas Palix <nicolas.palix@imag.fr>,
Ding Xiang <dingxiang@cmss.chinamobile.com>,
Coccinelle <cocci@systeme.lip6.fr>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [v2] Coccinelle: Suppression of warnings?
Date: Mon, 1 Jul 2019 14:40:43 +0200 [thread overview]
Message-ID: <eb95005d-e685-0a8f-416c-1a30ad3fbaa0@web.de> (raw)
In-Reply-To: <0b48a5c5-0814-6414-39ba-beb1b8b5253a@metux.net>
> By the way: do we have any mechanism for explicitly suppressing
> individual warnings (some kind of annotation),
I do not know such an accepted specification interface
(for the handling together with SmPL scripts) so far.
How would you identify possibly unwanted messages in a safe way?
> when the maintainer is sure that some particular case is a false-positive ?
Do you know any specific source code places already where you would get
concerned about the confidence and relevance of the provided information?
Regards,
Markus
next prev parent reply other threads:[~2019-07-01 12:41 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 17:30 [Cocci] [PATCH] Coccinelle: Add a SmPL script for the reconsideration of redundant dev_err() calls Markus Elfring
2019-06-20 17:30 ` Markus Elfring
2019-06-20 17:30 ` Markus Elfring
2019-06-20 18:48 ` [Cocci] " Julia Lawall
2019-06-20 18:48 ` Julia Lawall
2019-06-20 18:48 ` Julia Lawall
2019-06-20 19:02 ` [Cocci] " Markus Elfring
2019-06-20 19:02 ` Markus Elfring
2019-06-20 19:02 ` Markus Elfring
2019-06-20 19:12 ` [Cocci] " Julia Lawall
2019-06-20 19:12 ` Julia Lawall
2019-06-20 19:12 ` Julia Lawall
2019-06-20 19:34 ` [Cocci] " Markus Elfring
2019-06-20 19:34 ` Markus Elfring
2019-06-20 19:34 ` Markus Elfring
2019-06-21 9:15 ` [Cocci] " Markus Elfring
2019-06-21 9:15 ` Markus Elfring
2019-06-21 9:15 ` Markus Elfring
2019-06-21 9:21 ` [Cocci] " Julia Lawall
2019-06-21 9:21 ` Julia Lawall
2019-06-21 9:21 ` Julia Lawall
2019-06-21 9:37 ` [Cocci] " Markus Elfring
2019-06-21 9:37 ` Markus Elfring
2019-06-21 9:37 ` Markus Elfring
2019-06-21 14:52 ` [Cocci] " Julia Lawall
2019-06-21 14:52 ` Julia Lawall
2019-06-21 14:52 ` Julia Lawall
2019-06-21 9:37 ` [Cocci] " Markus Elfring
2019-06-21 9:37 ` Markus Elfring
2019-06-21 9:37 ` Markus Elfring
2019-06-20 19:02 ` [Cocci] " Markus Elfring
2019-06-20 19:02 ` Markus Elfring
2019-06-20 19:02 ` Markus Elfring
2019-07-01 8:10 ` [Cocci] [PATCH v2] " Markus Elfring
2019-07-01 8:10 ` Markus Elfring
2019-07-01 8:10 ` Markus Elfring
2019-07-01 10:48 ` [Cocci] " Enrico Weigelt, metux IT consult
2019-07-01 10:48 ` Enrico Weigelt, metux IT consult
2019-07-01 10:48 ` Enrico Weigelt, metux IT consult
2019-07-01 12:40 ` Markus Elfring [this message]
2019-07-01 12:40 ` [v2] Coccinelle: Suppression of warnings? Markus Elfring
2019-07-01 12:40 ` Markus Elfring
2019-07-01 12:47 ` [Cocci] [PATCH v2] Coccinelle: Add a SmPL script for the reconsideration of redundant dev_err() calls Julia Lawall
2019-07-01 12:47 ` Julia Lawall
2019-07-01 12:47 ` Julia Lawall
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=eb95005d-e685-0a8f-416c-1a30ad3fbaa0@web.de \
--to=markus.elfring@web.de \
--cc=cocci@systeme.lip6.fr \
--cc=dingxiang@cmss.chinamobile.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metux.net \
--cc=michal.lkml@markovi.net \
--cc=nicolas.palix@imag.fr \
/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.