From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] lua*: regeneration of Config.in
Date: Mon, 31 Dec 2018 17:58:22 +0100 [thread overview]
Message-ID: <20181231175822.7d2abd02@windsurf> (raw)
In-Reply-To: <20181219081707.1983-4-francois.perrad@gadz.org>
Hello Fran?ois,
On Wed, 19 Dec 2018 09:17:05 +0100, Francois Perrad wrote:
> diff --git a/package/ljlinenoise/Config.in b/package/ljlinenoise/Config.in
> index e6b587e65..26e79e23b 100644
> --- a/package/ljlinenoise/Config.in
> +++ b/package/ljlinenoise/Config.in
> @@ -1,9 +1,7 @@
> config BR2_PACKAGE_LJLINENOISE
> bool "ljlinenoise"
> - # ljsyscall is specifically for LuaJIT, not Lua.
I think this was useful to keep.
> diff --git a/package/ljsyscall/Config.in b/package/ljsyscall/Config.in
> index 3af9dabe9..601d0b122 100644
> --- a/package/ljsyscall/Config.in
> +++ b/package/ljsyscall/Config.in
> @@ -1,12 +1,11 @@
> config BR2_PACKAGE_LJSYSCALL
> bool "ljsyscall"
> - # ljsyscall is specifically for LuaJIT, not Lua.
And this as well.
So I've re-added those two lines when applying the patch.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-12-31 16:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 8:17 [Buildroot] [PATCH v3] luarocks addon Francois Perrad
2018-12-19 8:17 ` [Buildroot] [PATCH v3] luarocks: add buildroot addon Francois Perrad
2018-12-31 17:06 ` Thomas Petazzoni
2018-12-19 8:17 ` [Buildroot] [PATCH v3] lua*: regeneration of *.mk files Francois Perrad
2018-12-19 8:17 ` [Buildroot] [PATCH v3] lua*: regeneration of Config.in Francois Perrad
2018-12-31 16:58 ` Thomas Petazzoni [this message]
2018-12-19 8:17 ` [Buildroot] [PATCH v3] lua*: regeneration of hash files Francois Perrad
2018-12-19 8:17 ` [Buildroot] [PATCH v3] pkg-luarocks: add per package upgrade target Francois Perrad
2018-12-31 16:57 ` [Buildroot] [PATCH v3] luarocks addon Thomas Petazzoni
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=20181231175822.7d2abd02@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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