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: <f96efb81-ac39-e64a-a8fc-f2f638e1f3c7@intel.com>
Date:   Tue, 11 Apr 2023 16:41:51 -0700
From:   Jesse Brandeburg <jesse.brandeburg@...el.com>
To:     Andrew Halaney <ahalaney@...hat.com>,
        <linux-kernel@...r.kernel.org>
CC:     <agross@...nel.org>, <andersson@...nel.org>,
        <konrad.dybcio@...aro.org>, <davem@...emloft.net>,
        <edumazet@...gle.com>, <kuba@...nel.org>, <pabeni@...hat.com>,
        <robh+dt@...nel.org>, <krzysztof.kozlowski+dt@...aro.org>,
        <vkoul@...nel.org>, <bhupesh.sharma@...aro.org>, <wens@...e.org>,
        <jernej.skrabec@...il.com>, <samuel@...lland.org>,
        <mturquette@...libre.com>, <peppe.cavallaro@...com>,
        <alexandre.torgue@...s.st.com>, <joabreu@...opsys.com>,
        <mcoquelin.stm32@...il.com>, <richardcochran@...il.com>,
        <linux@...linux.org.uk>, <veekhee@...le.com>,
        <tee.min.tan@...ux.intel.com>, <mohammad.athari.ismail@...el.com>,
        <jonathanh@...dia.com>, <ruppala@...dia.com>, <bmasney@...hat.com>,
        <andrey.konovalov@...aro.org>, <linux-arm-msm@...r.kernel.org>,
        <netdev@...r.kernel.org>, <devicetree@...r.kernel.org>,
        <linux-stm32@...md-mailman.stormreply.com>,
        <linux-arm-kernel@...ts.infradead.org>, <ncai@...cinc.com>,
        <jsuraj@....qualcomm.com>, <hisunil@...cinc.com>,
        <echanude@...hat.com>, Simon Horman <simon.horman@...igine.com>
Subject: Re: [PATCH net-next v4 07/12] net: stmmac: Remove some unnecessary
 void pointers

On 4/11/2023 1:04 PM, Andrew Halaney wrote:
> There's a few spots in the hardware interface where a void pointer is
> used, but what's passed in and later cast out is always the same type.
> 
> Just use the proper type directly.
> 
> Reviewed-by: Simon Horman <simon.horman@...igine.com>
> Signed-off-by: Andrew Halaney <ahalaney@...hat.com>

Much better!

Reviewed-by: Jesse Brandeburg <jesse.brandeburg@...el.com>


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ