From: Markus Elfring <Markus.Elfring@web.de>
To: Ricardo Ribalda <ribalda@chromium.org>,
Julia Lawall <Julia.Lawall@inria.fr>,
cocci@inria.fr
Cc: LKML <linux-kernel@vger.kernel.org>,
Denis Efremov <efremov@linux.com>,
Nicolas Palix <nicolas.palix@imag.fr>
Subject: Re: [cocci] coccinelle: misc: minmax: Suppress reports for err returns
Date: Wed, 17 Apr 2024 15:02:52 +0200 [thread overview]
Message-ID: <ba67e3ac-33c4-4ced-86ca-fc590ca0ed36@web.de> (raw)
In-Reply-To: <CANiDSCtZzAs0u2tqJGRaJz6iqCTu_p-j_rkyGU7a9HFqUbJEMg@mail.gmail.com>
>> Adjustments for functionality of coccicheck operation modes can be clarified further.
>
> https://lore.kernel.org/lkml/2024041643-unshaven-happiest-1405@gregkh/
I hope that remaining communication difficulties can be resolved in more constructive ways.
Do you get further development ideas from previous contributions on presented topics?
Regards,
Markus
WARNING: multiple messages have this Message-ID (diff)
From: Markus Elfring <Markus.Elfring@web.de>
To: Ricardo Ribalda <ribalda@chromium.org>,
Julia Lawall <Julia.Lawall@inria.fr>,
cocci@inria.fr
Cc: LKML <linux-kernel@vger.kernel.org>,
Denis Efremov <efremov@linux.com>,
Nicolas Palix <nicolas.palix@imag.fr>
Subject: Re: coccinelle: misc: minmax: Suppress reports for err returns
Date: Wed, 17 Apr 2024 15:02:52 +0200 [thread overview]
Message-ID: <ba67e3ac-33c4-4ced-86ca-fc590ca0ed36@web.de> (raw)
In-Reply-To: <CANiDSCtZzAs0u2tqJGRaJz6iqCTu_p-j_rkyGU7a9HFqUbJEMg@mail.gmail.com>
>> Adjustments for functionality of coccicheck operation modes can be clarified further.
>
> https://lore.kernel.org/lkml/2024041643-unshaven-happiest-1405@gregkh/
I hope that remaining communication difficulties can be resolved in more constructive ways.
Do you get further development ideas from previous contributions on presented topics?
Regards,
Markus
next prev parent reply other threads:[~2024-04-17 13:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 21:15 [cocci] [PATCH] coccinelle: misc: minmax: Suppress reports for err returns Ricardo Ribalda
2024-04-15 21:15 ` Ricardo Ribalda
2024-04-16 8:32 ` [cocci] " Julia Lawall
2024-04-16 8:32 ` Julia Lawall
2024-04-16 11:30 ` [cocci] " Markus Elfring
2024-04-16 11:30 ` Markus Elfring
2024-04-16 11:32 ` [cocci] " Ricardo Ribalda
2024-04-16 11:32 ` Ricardo Ribalda
2024-04-16 11:50 ` [cocci] " Markus Elfring
2024-04-16 11:50 ` Markus Elfring
2024-04-17 11:13 ` Ricardo Ribalda
2024-04-17 13:02 ` Markus Elfring [this message]
2024-04-17 13:02 ` Markus Elfring
2024-04-18 20:55 ` [cocci] [PATCH] " Julia Lawall
2024-04-19 6:51 ` Markus Elfring
2024-04-19 7:01 ` 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=ba67e3ac-33c4-4ced-86ca-fc590ca0ed36@web.de \
--to=markus.elfring@web.de \
--cc=Julia.Lawall@inria.fr \
--cc=cocci@inria.fr \
--cc=efremov@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.palix@imag.fr \
--cc=ribalda@chromium.org \
/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.