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: <e53a03cf-71ce-1864-5700-b48e8beb17a6@amd.com>
Date:   Wed, 12 Apr 2023 11:28:44 -0500
From:   "Limonciello, Mario" <mario.limonciello@....com>
To:     Herbert Xu <herbert@...dor.apana.org.au>
Cc:     Wolfram Sang <wsa@...nel.org>,
        Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        Mika Westerberg <mika.westerberg@...ux.intel.com>,
        Jan Dabros <jsd@...ihalf.com>, linux-crypto@...r.kernel.org,
        linux-i2c@...r.kernel.org, Held Felix <Felix.Held@....com>,
        linux-kernel@...r.kernel.org,
        Mark Hasemeyer <markhas@...omium.org>,
        Grzegorz Bernacki <gjb@...ihalf.com>
Subject: Re: [PATCH v8 0/6] Use CCP driver to handle PSP I2C arbitration

On 4/7/2023 01:18, Wolfram Sang wrote:
> 
>>> How should this go upstream, i.e. are there dependencies? Shall I pick
>>> the I2C patches or is it better if all goes via the crypto tree?
>>>
>> IMO it's better to go through the crypto tree.  There are dependencies
>> in the crypto part from the earlier series that was merged.
> 
> Ok, fine with me. I acked the I2C patches. Thanks for the heads up.
> 

Herbert,

Would you mind to queue these up for -next?  I do have some other 
separate work I will be submitting that is going to layer on top of 
them, so I'd like to base it off your branch with these landed.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ