linux-kernel - Re: [PATCH v6 08/17] firmware: arm_scmi: Add priv parameter to scmi_rx

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: <20210728142625.zbx7zbeffwsksjl5@bogus>
Date:   Wed, 28 Jul 2021 15:26:25 +0100
From:   Sudeep Holla <sudeep.holla@....com>
To:     Cristian Marussi <cristian.marussi@....com>
Cc:     linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        virtualization@...ts.linux-foundation.org,
        virtio-dev@...ts.oasis-open.org, james.quinlan@...adcom.com,
        Jonathan.Cameron@...wei.com, f.fainelli@...il.com,
        etienne.carriere@...aro.org, vincent.guittot@...aro.org,
        souvik.chakravarty@....com, igor.skalkin@...nsynergy.com,
        peter.hilber@...nsynergy.com, alex.bennee@...aro.org,
        jean-philippe@...aro.org, mikhail.golubev@...nsynergy.com,
        anton.yakovlev@...nsynergy.com, Vasyl.Vavrychuk@...nsynergy.com,
        Andriy.Tryshnivskyy@...nsynergy.com
Subject: Re: [PATCH v6 08/17] firmware: arm_scmi: Add priv parameter to
 scmi_rx_callback

On Mon, Jul 12, 2021 at 03:18:24PM +0100, Cristian Marussi wrote:
> Add a new opaque void *priv parameter to scmi_rx_callback which can be
> optionally provided by the transport layer when invoking scmi_rx_callback
> and that will be passed back to the transport layer in xfer->priv.
> 
> This can be used by transports that needs to keep track of their specific
> data structures together with the valid xfers.
>

This change looks simple but doesn't make sense on its own. I assume you don't
want to add all these in the patch making use of priv which makes sense. Not
sure if the next patch uses it, but I prefer to keep them as close as possible
if it is not too much of a hassle.

-- 
Regards,
Sudeep