On 02/09/2016 08:49 AM, David Howells wrote:
> Are these in a public git branch somewhere that I can just merge?
>
No, after Herbert reverted them they only exist as separate patches:
https://patchwork.kernel.org/patch/8193021/raw/
https://patchwork.kernel.org/patch/8193001/raw/
Are these in a public git branch somewhere that I can just merge?
David
On 02/09/2016 08:49 AM, David Howells wrote:
> Are these in a public git branch somewhere that I can just merge?
>
No, after Herbert reverted them they only exist as separate patches:
https://patchwork.kernel.org/patch/8193021/raw/
https://patchwork.kernel.org/patch/8193001/raw/
Are these in a public git branch somewhere that I can just merge?
David
On Sun, Feb 07, 2016 at 12:43:53AM +, David Howells wrote:
>
> Ummm. I did say I'd take it on top of my patches. How did you take it? Did
> you merge Tadeusz's branch? If so, I can probably merge it into mine also and
> git will Just Do The Right Thing™.
No I merged them as individual
Herbert Xu wrote:
> > Hmmm... That means that the crypto branch and the security branch are going
> > to conflict.
>
> I thought you were OK with it going in now as you said that you'll
> fix it up later. Sorry for the misunderstanding. Do you want me to
> revert?
Ummm. I did say I'd take
On Sat, Feb 06, 2016 at 10:00:21AM +, David Howells wrote:
>
> Hmmm... That means that the crypto branch and the security branch are going
> to conflict.
I thought you were OK with it going in now as you said that you'll
fix it up later. Sorry for the misunderstanding. Do you want me to
Herbert Xu wrote:
> Applied.
Hmmm... That means that the crypto branch and the security branch are going
to conflict.
David
Herbert Xu wrote:
> > Hmmm... That means that the crypto branch and the security branch are going
> > to conflict.
>
> I thought you were OK with it going in now as you said that you'll
> fix it up later. Sorry for the misunderstanding. Do you want me to
>
On Sun, Feb 07, 2016 at 12:43:53AM +, David Howells wrote:
>
> Ummm. I did say I'd take it on top of my patches. How did you take it? Did
> you merge Tadeusz's branch? If so, I can probably merge it into mine also and
> git will Just Do The Right Thing™.
No I merged them as individual
On Sat, Feb 06, 2016 at 10:00:21AM +, David Howells wrote:
>
> Hmmm... That means that the crypto branch and the security branch are going
> to conflict.
I thought you were OK with it going in now as you said that you'll
fix it up later. Sorry for the misunderstanding. Do you want me to
Herbert Xu wrote:
> Applied.
Hmmm... That means that the crypto branch and the security branch are going
to conflict.
David
On Tue, Feb 02, 2016 at 10:08:48AM -0800, Tadeusz Struk wrote:
> Resend v5 rebased on top of 4.5
>
> This patch set converts the module verification and digital signature
> code to the new akcipher API.
> RSA implementation has been removed from crypto/asymmetric_keys and the
> new API is used
On Tue, Feb 02, 2016 at 10:08:48AM -0800, Tadeusz Struk wrote:
> Resend v5 rebased on top of 4.5
>
> This patch set converts the module verification and digital signature
> code to the new akcipher API.
> RSA implementation has been removed from crypto/asymmetric_keys and the
> new API is used
Resend v5 rebased on top of 4.5
This patch set converts the module verification and digital signature
code to the new akcipher API.
RSA implementation has been removed from crypto/asymmetric_keys and the
new API is used for cryptographic primitives.
There is no need for MPI above the akcipher API
Resend v5 rebased on top of 4.5
This patch set converts the module verification and digital signature
code to the new akcipher API.
RSA implementation has been removed from crypto/asymmetric_keys and the
new API is used for cryptographic primitives.
There is no need for MPI above the akcipher API
This patch set converts the module verification and digital signature
code to the new akcipher API.
RSA implementation has been removed from crypto/asymmetric_keys and the
new API is used for cryptographic primitives.
There is no need for MPI above the akcipher API anymore.
Modules can be verified
This patch set converts the module verification and digital signature
code to the new akcipher API.
RSA implementation has been removed from crypto/asymmetric_keys and the
new API is used for cryptographic primitives.
There is no need for MPI above the akcipher API anymore.
Modules can be verified
18 matches
Mail list logo