[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e514a05f-6e9f-1d62-9b38-163e13578bff@web.de>
Date: Mon, 12 Aug 2019 12:00:45 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Alexander Popov <alex.popov@...ux.com>, Jann Horn <jannh@...gle.com>,
Julia Lawall <julia.lawall@...6.fr>, kernel-janitors@...r.kernel.org,
cocci@...teme.lip6.fr
Cc: linux-kernel@...r.kernel.org, linux-block@...r.kernel.org,
kernel-hardening@...ts.openwall.com, Al Viro <viro@...iv.linux.org.uk>,
Denis Efremov <efremov@...ux.com>, Gilles Muller <Gilles.Muller@...6.fr>,
Jens Axboe <axboe@...nel.dk>, Jiri Kosina <jikos@...nel.org>,
Michal Marek <michal.lkml@...kovi.net>, Mukesh Ojha <mojha@...eaurora.org>,
Nicolas Palix <nicolas.palix@...g.fr>
Subject: Re: floppy: fix usercopy direction
> …, I see `exists` allows to drop `<+ +>`, right?
I would interpret the combination of such SmPL specifications in a different way.
> It turned out that sparse already can find these bugs.
This is generally nice, isn't it?
> Is this rule useful anyway?
I hope so.
Can scripts for the semantic patch language help any more?
> If so, I can prepare a patch.
Would you like to take corresponding adjustments into account?
Regards,
Markus
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
