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-next>] [day] [month] [year] [list]
Message-ID: <ZGKFV/FGu3oDNMV1@francesco-nb.int.toradex.com>
Date:   Mon, 15 May 2023 21:17:43 +0200
From:   Francesco Dolcini <francesco@...cini.it>
To:     Matthieu Baerts <matthieu.baerts@...sares.net>
Cc:     Andy Whitcroft <apw@...onical.com>, Joe Perches <joe@...ches.com>,
        Dwaipayan Ray <dwaipayanray1@...il.com>,
        Lukas Bulwahn <lukas.bulwahn@...il.com>,
        David Airlie <airlied@...il.com>,
        Thorsten Leemhuis <linux@...mhuis.info>,
        linux-kernel@...r.kernel.org
Subject: Reported-by checkpatch warning from v6.4-rc1

Hello,
starting from commit d6ccdd678e45 ("checkpatch: check for misuse of the link tags")
any Reported-by: tag not followed by a Closes trigger a warning, even if
we have a Link: tag afterward.

Example:

WARNING: Reported-by: should be immediately followed by Closes: with a URL to the report
#8:
Reported-by: kernel test robot <lkp@...el.com>
Link: https://lore.kernel.org/oe-kbuild-all/202305152341.oiSjRpv6-lkp@intel.com/
total: 0 errors, 1 warnings, 8 lines checked

>From what I can understand it was not in the intention of that patch,
and Link: is still fine to be used.

Comments?

Francesco


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ