From: Markus Elfring <Markus.Elfring@web.de>
To: Dejin Zheng <zhengdejin5@gmail.com>,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
Coccinelle <cocci@systeme.lip6.fr>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
"Andy Shevchenko" <andy.shevchenko@gmail.com>,
"Bartlomiej Zolnierkiewicz" <b.zolnierkie@samsung.com>,
"Florian Tobias Schandinat" <FlorianSchandinat@gmx.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Ralf Bächle" <ralf@linux-mips.org>,
"Thomas Bogendörfer" <tsbogend@alpha.franken.de>,
"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: console: Complete exception handling in newport_probe()
Date: Thu, 23 Apr 2020 19:22:02 +0200 [thread overview]
Message-ID: <68178ac9-ae0c-2f97-2620-38393741b3a1@web.de> (raw)
In-Reply-To: <20200423170245.GA3417@nuc8i5>
>>>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/scripts/coccinelle/free/iounmap.cocci
…
> Sorry, I do not know how to use the SmPL script.
I proposed to take another look at the header of such a file.
I imagine that provided information can trigger further development ideas
for the continuation of a constructive patch review.
>> Would you like to let any more source code analysis tools help you
>> to find remaining update candidates?
>>
> yes, but I think the source code analysis tools only can found the simple
> repetitive issue.
I suggest to reconsider this view.
> and need spend some time learning to use it.
This approach can be usual.
> at different stages, it should have different methods for me.
I hope so.
> now, I think the best for me may be that read and check the source code.
This can be also usual for a while.
I am curious how much special tools can make your software developments
more convenient and safe over time.
Regards,
Markus
next prev parent reply other threads:[~2020-04-23 17:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 11:10 [PATCH v1] console: fix an issue about ioremap leak Markus Elfring
2020-04-23 14:29 ` Dejin Zheng
2020-04-23 15:23 ` console: Complete exception handling in newport_probe() Markus Elfring
2020-04-23 17:02 ` Dejin Zheng
2020-04-23 17:22 ` Markus Elfring [this message]
2020-04-23 17:32 ` Greg Kroah-Hartman
2020-04-23 17:43 ` Markus Elfring
2020-04-24 7:46 ` 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=68178ac9-ae0c-2f97-2620-38393741b3a1@web.de \
--to=markus.elfring@web.de \
--cc=FlorianSchandinat@gmx.de \
--cc=andy.shevchenko@gmail.com \
--cc=b.zolnierkie@samsung.com \
--cc=cocci@systeme.lip6.fr \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=tglx@linutronix.de \
--cc=tsbogend@alpha.franken.de \
--cc=zhengdejin5@gmail.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
all inboxes | Powered by JetHome®