[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <782fd1c3-80ff-a296-b3a2-351257bb13b3@web.de>
Date: Sun, 17 Feb 2019 13:00:47 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Julia Lawall <julia.lawall@...6.fr>
Cc: Wen Yang <yellowriver2010@...mail.com>,
Gilles Muller <Gilles.Muller@...6.fr>,
Nicolas Palix <nicolas.palix@...g.fr>,
Michal Marek <michal.lkml@...kovi.net>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Wen Yang <wen.yang99@....com.cn>,
Cheng Shengyu <cheng.shengyu@....com.cn>,
kernel-janitors@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>,
Coccinelle <cocci@...teme.lip6.fr>
Subject: Re: [v6] coccinelle: semantic code search for missing put_device()
>> Would you dare to interpret my update suggestion (reordering of two identifiers)
>> as a required SmPL script correction?
>
> I didn't suggest to reorder anything.
This is obvious according to your acknowledgement for the sixth version
of this evolving SmPL script.
> Both are needed.
If you would insist on the specification of such an assignment exclusion
for a SmPL ellipsis:
Can we agree on a correct order?
> And, no I don't consider it to be a required suggestion.
Have we got a different view about an implementation detail at this place?
> In practice, reassigning such a variable is very unlikely.
This can be.
Regards,
Markus
Powered by blists - more mailing lists