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: "Thomas Bogendörfer" <tsbogend@alpha.franken.de>,
"Florian Tobias Schandinat" <FlorianSchandinat@gmx.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Bartlomiej Zolnierkiewicz" <b.zolnierkie@samsung.com>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
"Ralf Bächle" <ralf@linux-mips.org>,
"Andy Shevchenko" <andy.shevchenko@gmail.com>,
"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: [Cocci] console: Complete exception handling in newport_probe()
Date: Thu, 23 Apr 2020 17:23:29 +0200 [thread overview]
Message-ID: <f054f00c-b813-e0c2-fe2e-30ccdec1ff46@web.de> (raw)
In-Reply-To: <20200423142909.GB1562@nuc8i5>
>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/scripts/coccinelle/free/iounmap.cocci
>>
>> How do you think about to extend presented software analysis approaches?
>>
> Sorry, I am not familiar with it, I don't know.
Do you find the comments helpful at the beginning of this SmPL script?
Would you like to let any more source code analysis tools help you
to find remaining update candidates?
Regards,
Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
WARNING: multiple messages have this Message-ID (diff)
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: "Thomas Bogendörfer" <tsbogend@alpha.franken.de>,
"Florian Tobias Schandinat" <FlorianSchandinat@gmx.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Bartlomiej Zolnierkiewicz" <b.zolnierkie@samsung.com>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
"Ralf Bächle" <ralf@linux-mips.org>,
"Andy Shevchenko" <andy.shevchenko@gmail.com>,
"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: console: Complete exception handling in newport_probe()
Date: Thu, 23 Apr 2020 15:23:29 +0000 [thread overview]
Message-ID: <f054f00c-b813-e0c2-fe2e-30ccdec1ff46@web.de> (raw)
In-Reply-To: <20200423142909.GB1562@nuc8i5>
>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/scripts/coccinelle/free/iounmap.cocci
>>
>> How do you think about to extend presented software analysis approaches?
>>
> Sorry, I am not familiar with it, I don't know.
Do you find the comments helpful at the beginning of this SmPL script?
Would you like to let any more source code analysis tools help you
to find remaining update candidates?
Regards,
Markus
WARNING: multiple messages have this Message-ID (diff)
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: "Thomas Bogendörfer" <tsbogend@alpha.franken.de>,
"Florian Tobias Schandinat" <FlorianSchandinat@gmx.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Bartlomiej Zolnierkiewicz" <b.zolnierkie@samsung.com>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
"Ralf Bächle" <ralf@linux-mips.org>,
"Andy Shevchenko" <andy.shevchenko@gmail.com>,
"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: console: Complete exception handling in newport_probe()
Date: Thu, 23 Apr 2020 17:23:29 +0200 [thread overview]
Message-ID: <f054f00c-b813-e0c2-fe2e-30ccdec1ff46@web.de> (raw)
In-Reply-To: <20200423142909.GB1562@nuc8i5>
>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/scripts/coccinelle/free/iounmap.cocci
>>
>> How do you think about to extend presented software analysis approaches?
>>
> Sorry, I am not familiar with it, I don't know.
Do you find the comments helpful at the beginning of this SmPL script?
Would you like to let any more source code analysis tools help you
to find remaining update candidates?
Regards,
Markus
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
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 17:23:29 +0200 [thread overview]
Message-ID: <f054f00c-b813-e0c2-fe2e-30ccdec1ff46@web.de> (raw)
In-Reply-To: <20200423142909.GB1562@nuc8i5>
>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/scripts/coccinelle/free/iounmap.cocci
>>
>> How do you think about to extend presented software analysis approaches?
>>
> Sorry, I am not familiar with it, I don't know.
Do you find the comments helpful at the beginning of this SmPL script?
Would you like to let any more source code analysis tools help you
to find remaining update candidates?
Regards,
Markus
next prev parent reply other threads:[~2020-04-23 15:24 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 11:10 [Cocci] [PATCH v1] console: fix an issue about ioremap leak Markus Elfring
2020-04-23 11:10 ` Markus Elfring
2020-04-23 11:10 ` Markus Elfring
2020-04-23 11:10 ` Markus Elfring
2020-04-23 11:10 ` Markus Elfring
2020-04-23 14:29 ` [Cocci] " Dejin Zheng
2020-04-23 14:29 ` Dejin Zheng
2020-04-23 14:29 ` Dejin Zheng
2020-04-23 14:29 ` Dejin Zheng
2020-04-23 15:23 ` Markus Elfring [this message]
2020-04-23 15:23 ` console: Complete exception handling in newport_probe() Markus Elfring
2020-04-23 15:23 ` Markus Elfring
2020-04-23 15:23 ` Markus Elfring
2020-04-23 17:02 ` [Cocci] " Dejin Zheng
2020-04-23 17:02 ` Dejin Zheng
2020-04-23 17:02 ` Dejin Zheng
2020-04-23 17:02 ` Dejin Zheng
2020-04-23 17:22 ` [Cocci] " Markus Elfring
2020-04-23 17:22 ` Markus Elfring
2020-04-23 17:22 ` Markus Elfring
2020-04-23 17:22 ` Markus Elfring
2020-04-23 17:32 ` [Cocci] " Greg Kroah-Hartman
2020-04-23 17:32 ` Greg Kroah-Hartman
2020-04-23 17:32 ` Greg Kroah-Hartman
2020-04-23 17:32 ` Greg Kroah-Hartman
2020-04-23 17:43 ` [Cocci] " Markus Elfring
2020-04-23 17:43 ` Markus Elfring
2020-04-23 17:43 ` Markus Elfring
2020-04-23 17:43 ` Markus Elfring
2020-04-24 7:46 ` [Cocci] " Markus Elfring
2020-04-24 7:46 ` Markus Elfring
2020-04-24 7:46 ` Markus Elfring
2020-04-24 7:46 ` Markus Elfring
-- strict thread matches above, loose matches on Subject: below --
2020-04-22 15:53 [PATCH v1] console: fix an issue about ioremap leak Dejin Zheng
2020-04-22 15:53 ` Dejin Zheng
2020-04-22 15:53 ` Dejin Zheng
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=f054f00c-b813-e0c2-fe2e-30ccdec1ff46@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 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.