From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
To: linux-wireless@vger.kernel.org
Cc: wireless-regdb@lists.infradead.org,
"Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Subject: [PATCH v2 5/6] crda: make ssl keys include stdint.h
Date: Mon, 28 Oct 2013 17:42:05 +0100 [thread overview]
Message-ID: <1382978526-23929-6-git-send-email-mcgrof@do-not-panic.com> (raw)
In-Reply-To: <1382978526-23929-1-git-send-email-mcgrof@do-not-panic.com>
This is required to fix compilation if we
move reglig to its own library.
Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
---
utils/key2pub.py | 2 ++
1 file changed, 2 insertions(+)
diff --git a/utils/key2pub.py b/utils/key2pub.py
index 4d85369..3e84cd2 100755
--- a/utils/key2pub.py
+++ b/utils/key2pub.py
@@ -59,6 +59,7 @@ def print_ssl_32(output, name, val):
def print_ssl(output, name, val):
import struct
+ output.write('#include <stdint.h>\n')
if len(struct.pack('@L', 0)) == 8:
return print_ssl_64(output, name, val)
else:
@@ -85,6 +86,7 @@ static struct pubkey keys[] = {
pass
def print_gcrypt(output, name, val):
+ output.write('#include <stdint.h>\n')
while val[0] == '\0':
val = val[1:]
output.write('static const uint8_t %s[%d] = {\n' % (name, len(val)))
--
1.8.4.rc3
next prev parent reply other threads:[~2013-10-28 16:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 16:42 [PATCH v2 0/6] crda: few more updates Luis R. Rodriguez
2013-10-28 16:42 ` [PATCH v2 1/6] crda: relicense under copyleft-next-0.3.0 Luis R. Rodriguez
2013-10-28 16:42 ` [PATCH v2 2/6] crda: fix -pedantic gcc compilation Luis R. Rodriguez
2013-10-28 16:42 ` [PATCH v2 3/6] crda: add regulatory domain stream parser Luis R. Rodriguez
2013-10-28 16:42 ` [PATCH v2 4/6] crda: add regulatory domain optimizer Luis R. Rodriguez
2013-10-28 16:42 ` Luis R. Rodriguez [this message]
2013-10-28 16:42 ` [PATCH v2 6/6] crda: make reglib a shared library Luis R. Rodriguez
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=1382978526-23929-6-git-send-email-mcgrof@do-not-panic.com \
--to=mcgrof@do-not-panic.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wireless-regdb@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).