From: David Howells <dhowells@redhat.com>
To: Mimi Zohar <zohar@linux.vnet.ibm.com>
Cc: dhowells@redhat.com, vgoyal@redhat.com, keyrings@linux-nfs.org,
linux-kernel@vger.kernel.org
Subject: Re: [Keyrings] [PATCH 1/9] Provide a binary to hex conversion function
Date: Fri, 12 Sep 2014 21:30:00 +0100 [thread overview]
Message-ID: <28503.1410553800@warthog.procyon.org.uk> (raw)
In-Reply-To: <1410552676.5187.211.camel@dhcp-9-2-203-236.watson.ibm.com>
Mimi Zohar <zohar@linux.vnet.ibm.com> wrote:
> How about using hex_byte_pack()?
It doesn't do a bufferful, only one byte.
David
next prev parent reply other threads:[~2014-09-12 20:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 19:05 [PATCH 0/9] KEYS: Improve asymmetric key and PKCS#7 handling David Howells
2014-09-12 19:05 ` [PATCH 1/9] Provide a binary to hex conversion function David Howells
2014-09-12 20:11 ` [Keyrings] " Mimi Zohar
2014-09-12 20:30 ` David Howells [this message]
2014-09-12 20:47 ` Joe Perches
2014-09-12 20:53 ` David Howells
2014-09-12 20:53 ` Mimi Zohar
2014-09-12 21:14 ` David Howells
2014-09-12 19:05 ` [PATCH 2/9] KEYS: Preparse match data David Howells
2014-09-12 19:05 ` [PATCH 3/9] KEYS: Remove key_type::def_lookup_type David Howells
2014-09-12 19:05 ` [PATCH 4/9] KEYS: Remove key_type::match in favour of overriding default by match_preparse David Howells
2014-09-12 19:05 ` [PATCH 5/9] KEYS: Make the key matching functions return bool David Howells
2014-09-12 19:05 ` [PATCH 6/9] KEYS: Implement binary asymmetric key ID handling David Howells
2014-09-12 19:05 ` [PATCH 7/9] KEYS: Overhaul key identification when searching for asymmetric keys David Howells
2014-09-12 19:05 ` [PATCH 8/9] PKCS#7: Better handling of unsupported crypto David Howells
2014-09-12 19:05 ` [PATCH 9/9] PKCS#7: Handle PKCS#7 messages that contain no X.509 certs David Howells
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=28503.1410553800@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=keyrings@linux-nfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@redhat.com \
--cc=zohar@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®