From: Markus Elfring <Markus.Elfring@web.de>
To: "Michel Dänzer" <michel.daenzer@mailbox.org>,
dri-devel@lists.freedesktop.org, kernel-janitors@vger.kernel.org,
"Daniel Vetter" <daniel@ffwll.ch>,
"David Airlie" <airlied@gmail.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
cocci@inria.fr, Simon Ser <contact@emersion.fr>
Subject: Re: [1/3] drm: property: One function call less in drm_property_create() after error detection
Date: Wed, 3 Jan 2024 19:08:25 +0100 [thread overview]
Message-ID: <93cfabee-9692-491c-8d38-dec142e90252@web.de> (raw)
In-Reply-To: <dd300771-851f-4cfb-b9a2-d87d2b4399aa@mailbox.org>
>>> Out of curiosity, what exactly did Coccinelle report?
>>
>> Some SmPL scripts from my own selection tend to point questionable implementation details out.
>
> That doesn't answer my question.
It should.
> Without seeing the actual Coccinelle report,
There is no “official” report according to the discussed patch which is triggered
by known advices for the application of labels in goto chains.
> I'll assume that it didn't actually call for this change.
Software development opinions are evolving accordingly.
Regards,
Markus
next prev parent reply other threads:[~2024-01-03 18:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-26 9:36 [PATCH 0/3] drm: property: Adjustments for three function implementations Markus Elfring
2023-12-26 9:38 ` [PATCH 1/3] drm: property: One function call less in drm_property_create() after error detection Markus Elfring
2024-01-03 15:16 ` Michel Dänzer
2024-01-03 16:24 ` Markus Elfring
2024-01-03 17:18 ` Michel Dänzer
2024-01-03 18:08 ` Markus Elfring [this message]
2024-01-04 9:26 ` [1/3] " Michel Dänzer
2024-01-04 12:21 ` Markus Elfring
2024-01-04 15:26 ` [PATCH 1/3] " Dan Carpenter
2023-12-26 9:40 ` [PATCH 2/3] drm: property: Delete an unnecessary initialisation in drm_property_create() Markus Elfring
2023-12-26 9:42 ` [PATCH 3/3] drm: property: Improve four size determinations Markus Elfring
2023-12-26 10:10 ` Simon Ser
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=93cfabee-9692-491c-8d38-dec142e90252@web.de \
--to=markus.elfring@web.de \
--cc=airlied@gmail.com \
--cc=cocci@inria.fr \
--cc=contact@emersion.fr \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=michel.daenzer@mailbox.org \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.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