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  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]
Date:   Thu, 15 Sep 2022 11:47:37 -0700
From:   Jeff Johnson <>
To:     Alex Elder <>, Alex Elder <>,
        "David S. Miller" <>,
        Eric Dumazet <>,
        Jakub Kicinski <>,
        Paolo Abeni <>,
        Mathieu Poirier <>,
        Srinivas Kandagatla <>,
        Kalle Valo <>, Andy Gross <>,
        Bjorn Andersson <>,
        Konrad Dybcio <>
CC:     <>, <>,
        <>, <>,
Subject: Re: [PATCH 0/4] Make QMI message rules const

Following up on:
On 9/13/2022 6:58 AM, Alex Elder wrote:
> Why aren't you changing the "ei_array" field in
> the qmi_elem_info structure to be const?  Or the
> "ei" field of the qmi_msg_handler structure?  And
> the qmi_response_type_v01_ei array (and so on)?

All of these suggestions were actually part of the prerequisite patch:

So I think all of the comments have been addressed.


Powered by blists - more mailing lists