linux-kernel - Re: [PATCH v10 00/13] Add Broadcom VK 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <6f34a285-76cf-b1fc-dc5c-c889e97d0d4c@broadcom.com>
Date:   Thu, 28 Jan 2021 22:10:51 -0800
From:   Scott Branden <scott.branden@...adcom.com>
To:     Olof Johansson <olof@...om.net>
Cc:     Arnd Bergmann <arnd@...db.de>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Kees Cook <keescook@...omium.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Broadcom Kernel Feedback List 
        <bcm-kernel-feedback-list@...adcom.com>,
        Desmond Yan <desmond.yan@...adcom.com>
Subject: Re: [PATCH v10 00/13] Add Broadcom VK driver



On 2021-01-28 8:02 p.m., Olof Johansson wrote:
> Scott,
>
> On Thu, Jan 28, 2021 at 4:30 PM Scott Branden
> <scott.branden@...adcom.com> wrote:
>> This patch series drops previous patches in [1]
>> that were incorporated by Kees Cook into patch series
>> "Introduce partial kernel_read_file() support" [2].
>>
>> Remaining patches are contained in this series to add Broadcom VK driver.
>> (which depends on request_firmware_into_buf API addition which has
>> now been accepted into the upstream kernel as of v5.10-rc1).
>>
>> [1] https://lore.kernel.org/lkml/20200706232309.12010-1-scott.branden@broadcom.com/
>> [2] https://lore.kernel.org/lkml/20201002173828.2099543-1-keescook@chromium.org/
>>
>> Changes from v9:
>>  - fix compile if CONFIG_TTY not set
>>  - use if-else statement instead of conditional expression in set_q_num
>>  - generate bcm_vk_msg_remove call in proper patch
>>    (was generated in tty patch when should be in msg patch)
> Did I miss something? Greg already applied v9, so any fixes on top
> needs to be new patches.
Sorry, was unfamiliar with the process of having changes in linux-next needing correcting.
I sent out new patches to correct these issues against linux-next now.
>
>
> -Olof
Thanks for providing correct process.

Scott