All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: "Julia Lawall" <julia.lawall@inria.fr>,
	"Jérémy Lefaure" <jeremy.lefaure@netatmo.com>,
	cocci@inria.fr, kernel-janitors@vger.kernel.org
Cc: Nicolas Palix <nicolas.palix@imag.fr>
Subject: Re: [cocci] [v5] coccinelle: Extend address test from ifaddr semantic patch to test expressions
Date: Mon, 4 Jul 2022 19:16:44 +0200	[thread overview]
Message-ID: <0002e8ee-e024-c576-f0e6-908d1734b886@web.de> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2207032345230.23263@hadrien>

>> This change aims at detecting an address test in more complex conditions
>> and not only in if statements.
…
>> v4 -> v5: Change semantic patch to match explicit tests to NULL +
>> improve commit message
…
> Applied, thanks.


Another intermediate software development result was achieved.


Would you eventually like to care for remaining change possibilities
according to the discussed SmPL code variants?

Regards,
Markus

  reply	other threads:[~2022-07-04 17:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-01 16:01 [cocci] [PATCH v5] coccinelle: Extend address test from ifaddr semantic patch to test expressions Jérémy LEFAURE
2022-07-01 16:55 ` Markus Elfring
2022-07-01 19:30 ` Markus Elfring
2022-07-01 20:49   ` Julia Lawall
2022-07-01 20:49     ` [cocci] " Julia Lawall
2022-07-01 21:13     ` [cocci] [v5] " Markus Elfring
2022-07-02  8:01     ` [cocci] [PATCH v5] " Markus Elfring
2022-07-02 10:21       ` Julia Lawall
2022-07-02 10:21         ` [cocci] " Julia Lawall
2022-07-02 11:00         ` [cocci] [v5] " Markus Elfring
2022-07-03 11:34         ` [cocci] [PATCH v5] " Markus Elfring
2022-07-03 10:50 ` Markus Elfring
2022-07-03 21:45 ` Julia Lawall
2022-07-04 17:16   ` Markus Elfring [this message]
2022-07-09  5:30   ` Markus Elfring

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=0002e8ee-e024-c576-f0e6-908d1734b886@web.de \
    --to=markus.elfring@web.de \
    --cc=cocci@inria.fr \
    --cc=jeremy.lefaure@netatmo.com \
    --cc=julia.lawall@inria.fr \
    --cc=kernel-janitors@vger.kernel.org \
    --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.