Re: [GIT PULL] KEYS: Changes for keyrings for security/next

2014-09-22 Thread David Howells
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

Re: [GIT PULL] KEYS: Changes for keyrings for security/next

2014-09-22 Thread James Morris
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

Re: [GIT PULL] KEYS: Changes for keyrings for security/next

2014-09-22 Thread James Morris
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

Re: [GIT PULL] KEYS: Changes for keyrings for security/next

2014-09-22 Thread David Howells
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

Re: [GIT PULL] KEYS: Changes for keyrings for security/next

2014-09-21 Thread David Howells
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

Re: [GIT PULL] KEYS: Changes for keyrings for security/next

2014-09-21 Thread David Howells
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

Re: [GIT PULL] KEYS: Changes for keyrings for security/next

2014-09-20 Thread David Howells
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,

Re: [GIT PULL] KEYS: Changes for keyrings for security/next

2014-09-20 Thread David Howells
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

Re: [GIT PULL] KEYS: Changes for keyrings for security/next

2014-09-19 Thread James Morris
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

Re: [GIT PULL] KEYS: Changes for keyrings for security/next

2014-09-19 Thread James Morris
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

[GIT PULL] KEYS: Changes for keyrings for security/next

2014-09-16 Thread David Howells
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

[GIT PULL] KEYS: Changes for keyrings for security/next

2014-09-16 Thread David Howells
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