linux-kernel - Re: [PATCH V2] soc: imx8m: Correct i.MX8MP UID fuse offset

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: <552e1ae9-8b28-a462-5ee8-3e5bd6821c90@nxp.com>
Date:   Wed, 10 Jun 2020 11:43:17 +0300
From:   Iuliana Prodan <iuliana.prodan@....com>
To:     Anson Huang <anson.huang@....com>,
        Aisheng Dong <aisheng.dong@....com>,
        "shawnguo@...nel.org" <shawnguo@...nel.org>,
        "s.hauer@...gutronix.de" <s.hauer@...gutronix.de>,
        "kernel@...gutronix.de" <kernel@...gutronix.de>,
        "festevam@...il.com" <festevam@...il.com>,
        Leonard Crestez <leonard.crestez@....com>,
        Abel Vesa <abel.vesa@....com>,
        "l.stach@...gutronix.de" <l.stach@...gutronix.de>,
        Peng Fan <peng.fan@....com>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Cc:     dl-linux-imx <linux-imx@....com>
Subject: Re: [PATCH V2] soc: imx8m: Correct i.MX8MP UID fuse offset



On 6/10/2020 10:57 AM, Anson Huang wrote:
> 
>> Subject: RE: [PATCH V2] soc: imx8m: Correct i.MX8MP UID fuse offset
>>
>>> From: Anson Huang <Anson.Huang@....com>
>>> Sent: Wednesday, June 10, 2020 6:42 AM
>>>
>>> Correct i.MX8MP UID fuse offset according to fuse map:
>>>
>>> UID_LOW: 0x420
>>> UID_HIGH: 0x430
>>>
>>> Fixes: fc40200ebf82 ("soc: imx: increase build coverage for imx8m soc
>>> driver")
>>
>> AFAIK "Fixes:" should point to the original patch which introduced the issue.
>> Not the one changing file name.
> 
> But the patch can NOT be applied to the kernel version with original file, how to
> fix it?
> 
I believe you can add two "Fixes:" with the two commits: the one 
introducing the issue and the one changing the file name.

Iulia