linux-kernel - Re: [GIT PULL] remoteproc updates for v5.13

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]

Date:   Tue, 4 May 2021 11:22:25 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Bjorn Andersson <bjorn.andersson@...aro.org>
Cc:     Ohad Ben-Cohen <ohad@...ery.com>, linux-remoteproc@...r.kernel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Mathieu Poirier <mathieu.poirier@...aro.org>,
        Peng Fan <peng.fan@....com>,
        Govind Singh <govinds@...eaurora.org>,
        Wei Yongjun <weiyongjun1@...wei.com>,
        Suman Anna <s-anna@...com>,
        Arnaud Pouliquen <arnaud.pouliquen@...s.st.com>,
        Manivannan Sadhasivam <mani@...nel.org>,
        Jindong Yue <jindong.yue@....com>,
        Junlin Yang <yangjunlin@...ong.com>,
        Raghavendra Rao Ananta <rananta@...eaurora.org>,
        Yang Li <yang.lee@...ux.alibaba.com>
Subject: Re: [GIT PULL] remoteproc updates for v5.13

On Tue, May 4, 2021 at 8:03 AM Bjorn Andersson
<bjorn.andersson@...aro.org> wrote:
>
> This adds support to the remoteproc core for detaching Linux from a
> running remoteproc, e.g. to reboot Linux while leaving the remoteproc
> running, and it enable this support in the stm32 remoteproc driver.

Honestly, when explaining new functionality like this, it would be
lovely to also give an example of the _why_, not just the what.

Ie, some concrete example of "this is useful to have the remoteproc
continue scanning wireless networks" or whatever.

I'm sure there's some actual use-case for this all, but neither the
pull request nor the individual commits seem to actually explain that
"why", only the "what".

I've pulled this, but hope that these kinds of issues can be explained
better.. I think a lot of people care more about "why" than some
implementation detail "what" cases.

              Linus