From: Julia Lawall <julia.lawall@inria.fr>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Markus Elfring <Markus.Elfring@web.de>,
cocci@inria.fr, kernel-janitors <kernel-janitors@vger.kernel.org>,
nicolas palix <nicolas.palix@imag.fr>,
linux-kernel <linux-kernel@vger.kernel.org>,
kernel@pengutronix.de
Subject: Re: [cocci] [PATCH] coccinelle: api: Don't use devm_platform_get_and_ioremap_resource with res==NULL
Date: Tue, 8 Nov 2022 06:51:53 +0100 (CET) [thread overview]
Message-ID: <257596884.6156222.1667886713273.JavaMail.zimbra@inria.fr> (raw)
In-Reply-To: <20221107200815.u7hcwejileeabnct@pengutronix.de>
> After uninstalling python2 this ends in:
>
> Cannot find Python library
> coccicheck failed
> make: *** [Makefile:2076: coccicheck] Error 255
>
> Didn't try to debug that any further. Is that worth a bug report against
> coccinelle (which is shipped by my distribution)?
>
> I tried to adapt the org and report modes from other patches in the same
> directory. So a critical glimpse by someone more knowledgable than me is
> recommended. However I don't know how to react to "I doubt ... is
> appropriate", I'd need a more constructive feedback to act on.
I'm not a python expert, so I'm not sure what to do about this python2 vs python3 problem. Is there some strategy for printing that works in both of them?
julia
next prev parent reply other threads:[~2022-11-08 5:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 11:47 [PATCH v1] " Uwe Kleine-König
2022-11-07 12:45 ` Julia Lawall
2022-11-07 18:11 ` [PATCH v2] " Uwe Kleine-König
2022-11-10 15:07 ` Uwe Kleine-König
[not found] ` <bd13da2d-6d18-4f33-0987-a193e3c9b761@web.de>
2022-11-07 20:08 ` [cocci] [PATCH] " Uwe Kleine-König
2022-11-08 5:51 ` Julia Lawall [this message]
2022-11-08 7:55 ` Nicolas Palix
2022-11-08 9:54 ` Uwe Kleine-König
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=257596884.6156222.1667886713273.JavaMail.zimbra@inria.fr \
--to=julia.lawall@inria.fr \
--cc=Markus.Elfring@web.de \
--cc=cocci@inria.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.palix@imag.fr \
--cc=u.kleine-koenig@pengutronix.de \
/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
all inboxes | Powered by JetHome®