From: Johannes Berg <johannes@sipsolutions.net>
To: Paul Menzel <pmenzel+linux-wireless@molgen.mpg.de>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: net/wireless/shipped-certs.c:2:1: error: expected expression at end of input
Date: Tue, 05 Dec 2017 11:03:39 +0100 [thread overview]
Message-ID: <1512468219.26976.15.camel@sipsolutions.net> (raw)
In-Reply-To: <4006aefb-e9af-d809-b45a-201d20e75f9d@molgen.mpg.de> (sfid-20171205_110226_118243_D9C78F49)
On Tue, 2017-12-05 at 11:01 +0100, Paul Menzel wrote:
>
>
> ```
> $ git describe
> v4.15-rc2-79-gfd6d2e506ce6
> $ git log --oneline -1
> fd6d2e506ce6 Merge tag 'docs-4.15-fixes' of git://git.lwn.net/linux
> $ time ARCH=i386 make deb-pkg -j50
> […]
> net/wireless/shipped-certs.c:2:1: error: expected expression at end of input
> const u8 shipped_regdb_certs[] = {
> ^~~~~
> […]
> $ more net/wireless/shipped-certs.c
> #include "reg.h"
> const u8 shipped_regdb_certs[] = {
> ```
Ah, here we go - you probably don't have "hexdump" installed on this
system?
I thought about doing hexdump in posix shell/awk/sed/whatever
instead... maybe I should do that.
johannes
next prev parent reply other threads:[~2017-12-05 10:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 10:01 net/wireless/shipped-certs.c:2:1: error: expected expression at end of input Paul Menzel
2017-12-05 10:03 ` Johannes Berg [this message]
2017-12-05 10:15 ` Paul Menzel
2017-12-05 10:31 ` Johannes Berg
2017-12-05 10:36 ` Paul Menzel
2017-12-13 7:53 ` Damian Tometzki
2017-12-13 9:16 ` Paul Menzel
2017-12-13 11:00 ` Damian Tometzki
2017-12-13 11:07 ` Paul Menzel
2017-12-13 13:33 ` Damian Tometzki
2017-12-13 14:19 ` Damian Tometzki
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=1512468219.26976.15.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pmenzel+linux-wireless@molgen.mpg.de \
/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