From: Markus Elfring <Markus.Elfring@web.de>
To: Sam Ravnborg <sam@ravnborg.org>,
Linus Walleij <linus.walleij@linaro.org>,
dri-devel@lists.freedesktop.org
Cc: kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@linux.ie>,
Tang Bin <tangbin@cmss.chinamobile.com>
Subject: Re: drm/tve200: Checking for a failed platform_get_irq() call in tve200_probe()
Date: Fri, 10 Apr 2020 14:25:57 +0200 [thread overview]
Message-ID: <9971df1b-0651-fac0-847f-cf07eefe8996@web.de> (raw)
In-Reply-To: <20200410121406.GA31761@ravnborg.org>
>> I found 20 source files from the software “Linux next-20200408”
>> which seem to contain similar update candidates.
>> Would you like to clarify any extensions for improved applications
>> of scripts with the semantic patch language (Coccinelle software)
>> for corresponding analysis and transformation purposes?
> Please just send a series of patches, one for each driver.
I am used to this possibility for years.
> Each changelog needs to explain the rationale behind the change.
I hope to achieve higher confidence also around specific checks
for return values of Linux functions so that unwanted misunderstandings
can be avoided for mentioned implementation details.
> As for coccinelle - I cannot help you.
I might help you more also by the means of this development tool
if related system factors can be improved somehow.
Regards,
Markus
prev parent reply other threads:[~2020-04-10 12:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 13:05 drm/tve200: Checking for a failed platform_get_irq() call in tve200_probe() Markus Elfring
2020-04-10 10:18 ` Sam Ravnborg
2020-04-10 10:56 ` Markus Elfring
2020-04-10 12:14 ` Sam Ravnborg
2020-04-10 12:25 ` Markus Elfring [this message]
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=9971df1b-0651-fac0-847f-cf07eefe8996@web.de \
--to=markus.elfring@web.de \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=tangbin@cmss.chinamobile.com \
/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;
as well as URLs for NNTP newsgroup(s).