linux-kernel - Re: [PATCH v6] firmware: google: Implement cbmem in sysfs driver

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 for Android: free password hash cracker in your pocket

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

Message-ID: <YuuBrUmiRYoaSmPw@google.com>
Date:   Thu, 4 Aug 2022 08:22:05 +0000
From:   Tzung-Bi Shih <tzungbi@...nel.org>
To:     Jack Rosenthal <jrosenth@...omium.org>
Cc:     linux-kernel@...r.kernel.org, chrome-platform@...ts.linux.dev,
        Stephen Boyd <swboyd@...omium.org>,
        Guenter Roeck <groeck@...omium.org>,
        Julius Werner <jwerner@...omium.org>,
        kernel test robot <lkp@...el.com>
Subject: Re: [PATCH v6] firmware: google: Implement cbmem in sysfs driver

On Tue, Aug 02, 2022 at 07:03:43AM -0700, Jack Rosenthal wrote:
> cbmem entries can be read from coreboot table
> 0x31 (LB_TAG_CBMEM_ENTRY).  This commit exports access to cbmem
> entries in sysfs under /sys/firmware/coreboot/cbmem-*.
> 
> Link: https://issuetracker.google.com/239604743

I doubt if the Link tag would be useful for public.

[...]

> Reported-by: kernel test robot <lkp@...el.com>

Suggest to drop the Reported-by tag even if the robot reported some compile
errors during the development.  Given that the patch isn't a fixup but
supporting something new (which isn't "reported by" the robot).