Re: [PATCH v5 0/2] Add support for ECDSA-signed kernel modules
From: Stefan Berger <stefanb@linux.ibm.com>
Date: 2021-06-10 11:50:11
Also in:
keyrings, linux-security-module, lkml
From: Stefan Berger <stefanb@linux.ibm.com>
Date: 2021-06-10 11:50:11
Also in:
keyrings, linux-security-module, lkml
On 6/10/21 5:03 AM, Jarkko Sakkinen wrote:
On Wed, Jun 09, 2021 at 09:58:29AM -0400, Stefan Berger wrote:quoted
On 6/9/21 8:44 AM, Jarkko Sakkinen wrote:quoted
On Thu, Jun 03, 2021 at 08:32:59AM -0400, Stefan Berger wrote:quoted
On 6/3/21 2:47 AM, Jarkko Sakkinen wrote:quoted
quoted
-- 2.29.2Please instead send a fix.We have a Fixes tag in 1/2, so we want this to propagate to older kernels and need the fix in 1/2 for that reason. StefanSo please do an additional fix and send it.1/2 is supposed to propagate to older kernels and needs to change as posted here in v5 (assuming that this does indeed fix what the build bot was complaining about). 2/2 also changes. A fix on top of v4 would fix 2/2 but won't apply cleanly to 1/2 as cannot easily propagate to older kernels. Is that what we want? Why can you not remove v4 from your queue and replace it with v5? StefanWhat you can do is to send fix or fixes with appropriate fixes tags and I can then squash them for appropriate patches. That's less work for me.
Once you squash a fix on top of existing 1/2 , existing 2/2 will not apply anymore. I am not sure what to send you. I think it would take less time to remove the existing 2 patches and replace them with v5. Stefan