James Morris wrote:
> Ok, pulled to my next branch.
Thanks!
David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
On Mon, 22 Sep 2014, David Howells wrote:
> James Morris wrote:
>
> > > Can you please pull these changes into security/next. They include the
> > > fixes
> > > tag I previously requested as there's a dependency between these changes
> > > and
> > > the fixes.
> > >
> >
> > I'm getting
On Mon, 22 Sep 2014, David Howells wrote:
James Morris jmor...@namei.org wrote:
Can you please pull these changes into security/next. They include the
fixes
tag I previously requested as there's a dependency between these changes
and
the fixes.
I'm getting this
James Morris jmor...@namei.org wrote:
Ok, pulled to my next branch.
Thanks!
David
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the
James Morris wrote:
> > Can you please pull these changes into security/next. They include the
> > fixes
> > tag I previously requested as there's a dependency between these changes and
> > the fixes.
> >
>
> I'm getting this warning after pulling your code:
>
> CC crypto/hash_info.o
James Morris jmor...@namei.org wrote:
Can you please pull these changes into security/next. They include the
fixes
tag I previously requested as there's a dependency between these changes and
the fixes.
I'm getting this warning after pulling your code:
CC
James Morris wrote:
> I'm getting this warning after pulling your code:
>
> CC crypto/hash_info.o
> crypto/asymmetric_keys/asymmetric_type.c: In function
> asymmetric_key_hex_to_key_id:
> crypto/asymmetric_keys/asymmetric_type.c:110: warning: ignoring return
> value of hex2bin,
James Morris jmor...@namei.org wrote:
I'm getting this warning after pulling your code:
CC crypto/hash_info.o
crypto/asymmetric_keys/asymmetric_type.c: In function
asymmetric_key_hex_to_key_id:
crypto/asymmetric_keys/asymmetric_type.c:110: warning: ignoring return
value of
On Tue, 16 Sep 2014, David Howells wrote:
> Hi James,
>
> Can you please pull these changes into security/next. They include the fixes
> tag I previously requested as there's a dependency between these changes and
> the fixes.
>
I'm getting this warning after pulling your code:
CC
On Tue, 16 Sep 2014, David Howells wrote:
Hi James,
Can you please pull these changes into security/next. They include the fixes
tag I previously requested as there's a dependency between these changes and
the fixes.
I'm getting this warning after pulling your code:
CC
Hi James,
Can you please pull these changes into security/next. They include the fixes
tag I previously requested as there's a dependency between these changes and
the fixes.
So, there are the fixes to go upstream:
(1) Reinstate the production of EPERM for key types beginning with '.' in
Hi James,
Can you please pull these changes into security/next. They include the fixes
tag I previously requested as there's a dependency between these changes and
the fixes.
So, there are the fixes to go upstream:
(1) Reinstate the production of EPERM for key types beginning with '.' in
12 matches
Mail list logo