linux-kernel - Re: [PATCH v2 1/3] iio: temperature: ltc2983: Don't hard code defined constants in messages

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]

Message-ID: <6937d748bb04b53b88d2f4363db31bed2ae7550a.camel@perches.com>
Date:   Mon, 07 Feb 2022 09:29:52 -0800
From:   Joe Perches <joe@...ches.com>
To:     Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc:     linux-iio@...r.kernel.org, linux-kernel@...r.kernel.org,
        Nuno Sá <nuno.sa@...log.com>,
        Jonathan Cameron <jic23@...nel.org>,
        Lars-Peter Clausen <lars@...afoo.de>
Subject: Re: [PATCH v2 1/3] iio: temperature: ltc2983: Don't hard code
 defined constants in messages

On Mon, 2022-02-07 at 19:21 +0200, Andy Shevchenko wrote:
> On Mon, Feb 07, 2022 at 08:37:55AM -0800, Joe Perches wrote:
> > On Mon, 2022-02-07 at 12:48 +0200, Andy Shevchenko wrote:
> > > In a couple of messages the constants, which have their definitions,
> > > are hard coded into the message text. Unhardcode them.
> > 
> > Found by inspection or tool?
> 
> Does it matter?

Yes.  If it was done using a tool, then it could used treewide.

> No, a side effect of the following patch.

k