linux-kernel - Re: scripts/coccicheck: Update for a comment?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 7 Oct 2016 08:27:21 +0200 (CEST)
From:   Julia Lawall <julia.lawall@...6.fr>
To:     SF Markus Elfring <elfring@...rs.sourceforge.net>
cc:     Julia Lawall <julia.lawall@...6.fr>,
        Coccinelle <cocci@...teme.lip6.fr>,
        Gilles Muller <Gilles.Muller@...6.fr>,
        Jonathan Corbet <corbet@....net>,
        "Luis R. Rodriguez" <mcgrof@...nel.org>,
        Michal Marek <mmarek@...e.com>,
        Nicolas Palix <nicolas.palix@...g.fr>,
        LKML <linux-kernel@...r.kernel.org>,
        kernel-janitors@...r.kernel.org
Subject: Re: scripts/coccicheck: Update for a comment?



On Fri, 7 Oct 2016, SF Markus Elfring wrote:

> >>>> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/tree/scripts/coccicheck?id=c802e87fbe2d4dd58982d01b3c39bc5a781223aa#n4
> >>>
> >>> How about submitting a patch to fix the problem?
> >>
> >> I would appreciate to become a bit more sure about the current storage location
> >> which should be referenced in this file.
> >
> > In the Documentation directory find . -name "*cocci*"
> >
> > gives
> >
> > ./dev-tools/coccinelle.rst
> >
> > I think you could have done that yourself.
>
> Does the usage of the format "reStructuredText" trigger further considerations
> like the following?
>
> * Does your feedback suggest that the path from this source file should be put
>   in related places?
>
> * Would it make sense to store such a file name in a special variable?
>
> * When would you refer to generated file formats (like PDF) for this use case?

Either you send the patch, or I will send the patch, when I have time,
with no credit to you.  I'm not an expert on all of the future plans for
the documentation,  The only think I know is where the file is now, and
that the file is perfectly readable in its rst format, and thus it seems
quite all right to reference it.  If the situation change in the future,
we can have another patch in the future.

julia