Thread (18 messages) 18 messages, 7 authors, 2016-09-14

Re: [PATCH 00/26] constify local structures

From: Jarkko Sakkinen <hidden>
Date: 2016-09-12 18:50:34
Also in: alsa-devel, kernel-janitors, linux-acpi, linux-can, linux-fbdev, linux-media, linux-pm, linux-rdma, linux-renesas-soc, linux-scsi, linux-spi, lkml, netdev, platform-driver-x86

On Mon, Sep 12, 2016 at 03:52:08PM +0200, Julia Lawall wrote:

On Mon, 12 Sep 2016, Felipe Balbi wrote:
quoted
Hi,

Jarkko Sakkinen [off-list ref] writes:
quoted
On Mon, Sep 12, 2016 at 10:54:07AM +0200, Julia Lawall wrote:
quoted

On Sun, 11 Sep 2016, Jarkko Sakkinen wrote:
quoted
On Sun, Sep 11, 2016 at 03:05:42PM +0200, Julia Lawall wrote:
quoted
Constify local structures.

The semantic patch that makes this change is as follows:
(http://coccinelle.lip6.fr/)
Just my two cents but:

1. You *can* use a static analysis too to find bugs or other issues.
2. However, you should manually do the commits and proper commit
   messages to subsystems based on your findings. And I generally think
   that if one contributes code one should also at least smoke test changes
   somehow.

I don't know if I'm alone with my opinion. I just think that one should
also do the analysis part and not blindly create and submit patches.
All of the patches are compile tested.  And the individual patches are
Compile-testing is not testing. If you are not able to test a commit,
you should explain why.
Dude, Julia has been doing semantic patching for years already and
nobody has raised any concerns so far. There's already an expectation
that Coccinelle *works* and Julia's sematic patches are sound.

Besides, adding 'const' is something that causes virtually no functional
changes to the point that build-testing is really all you need. Any
problems caused by adding 'const' to a definition will be seen by build
errors or warnings.

Really, just stop with the pointless discussion and go read a bit about
Coccinelle and what semantic patches are giving you. The work done by
Julia and her peers are INRIA have measurable benefits.

You're really making a thunderstorm in a glass of water.
Thanks for the defense, but since a lot of these patches torned out to be
wrong, due to an incorrect parse by Coccinelle, combined with an
unpleasantly lax compiler, Jarkko does have a point that I should have
looked at the patches more carefully.  In any case, I have written to the
maintainers relevant to the patches that turned out to be incorrect.
Exactly. I'm not excepting that every commit would require extensive
analysis but it would be good to quickly at least skim through commits
and see if they make sense (or ask if unsure) :) 

And I'm fine with compile testing if it is mentioned in the commit msg.
julia
/Jarkko
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help