[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOesGMgzKKjOBHYM=eodZPm0rE=_oF9o_jjBudQ-Ef8gYFFMfg@mail.gmail.com>
Date: Thu, 28 Jan 2021 20:02:46 -0800
From: Olof Johansson <olof@...om.net>
To: Scott Branden <scott.branden@...adcom.com>
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
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.
-Olof
Powered by blists - more mailing lists