Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] lua: needs dynamic library support (dlopen)
Date: Sun, 23 Feb 2014 20:16:40 +0100	[thread overview]
Message-ID: <20140223201640.145e11f7@skate> (raw)
In-Reply-To: <CAB0FRssLEc6ntNwO53oDL-+yNSnBkBnP=wr7VAS3ox2WZ+HsCA@mail.gmail.com>

Dear Fran?ois Perrad,

On Sun, 23 Feb 2014 19:15:41 +0100, Fran?ois Perrad wrote:

> >>No, that's not the correct fix. The correct fix is a variant of
> >>http://patchwork.ozlabs.org/patch/313208/, which as suggested by Peter
> >>should use BR2_PREFER_STATIC_LIB as a condition, and not
> >>BR2_BINFMT_FLAT.
> >
> > Ok, understood.
> > Francois, what are your plans with that patch?
> 
> http://patchwork.ozlabs.org/patch/313208/ is a V1 with BR2_BINFMT_FLAT.
> I've already send a V2, see
> http://patchwork.ozlabs.org/patch/314145/ --> lua: refactor install steps
> http://patchwork.ozlabs.org/patch/314146/ --> lua: handles BR2_PREFER_STATIC_LIB
> 
> Note: V1 fixes only compilation issue, V2 handles compilation,
> linking, and installation

Generally speaking, I would recommend you (and I believe I already did)
to write more detailed commit logs. It would clearly help to get your
patches merged. Your first patch has absolutely no information, and
your second patch only references the autobuilder failure.

As a rule of thumb, if your patch is not trivial, there should at least
be 2 or 3 paragraphs of text in the commit log. If there is not 2 or 3
paragraphs, then you should, before sending the patch, wonder if there
is really enough information for an external reviewer to understand
what's going on.

I really, really appreciate all your contributions, and I would like to
see them merged faster. And to help achieve this, better commit logs is
definitely a key thing.

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2014-02-23 19:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-23 17:19 [Buildroot] [PATCH] lua: needs dynamic library support (dlopen) Thomas De Schampheleire
2014-02-23 17:38 ` Thomas Petazzoni
2014-02-23 17:49   ` Thomas De Schampheleire
2014-02-23 18:15     ` François Perrad
2014-02-23 19:16       ` Thomas Petazzoni [this message]

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=20140223201640.145e11f7@skate \
    --to=thomas.petazzoni@free-electrons.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