All of lore.kernel.org
 help / color / mirror / Atom feed
From: Asaf Kahlon <asafka7@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] zeromq: check if -latomic is needed
Date: Tue, 08 May 2018 03:46:21 +0000	[thread overview]
Message-ID: <CALFsTFV4MUFtydH3nC2M=h5W+3bn+gp54MAciwOzGKEvddym8g@mail.gmail.com> (raw)
In-Reply-To: <20180507232430.7d507c55@windsurf>

Sure, I'll send an update on the upstream.
Would it be necessary to send a new patch here? It will probably be the
same code, just the pull request link on the commit message will change
(and we won't be able to have a link with all the patch anyway since half
of it was already merged).

Thanks,
Asaf.

On Tue, May 8, 2018, 00:24 Thomas Petazzoni <thomas.petazzoni@bootlin.com>
wrote:

> Hello,
>
> On Mon,  7 May 2018 23:26:23 +0300, Asaf Kahlon wrote:
> > Fixes:
> >
> http://autobuild.buildroot.net/results/b149aa2ee00e4d6a53c884cf99ecb2dd8af58b65/
> >
> http://autobuild.buildroot.net/results/e4b3616ac2695d3b6898185a70da6509b1faa2b8/
> >
> > Patch the package to check if -latomic is needed to be added, depending
> on the
> > result of AC_LINK_IFELSE.
>
> Thanks for this new iteration.
>
> > The patch was sent to upstream, see:
> > https://github.com/zeromq/libzmq/pull/3083
>
> Sadly, this pull request corresponds to the previous iteration, and it
> has been merged. Perhaps you can send a follow-up patch upstream to
> improve the situation ?
>
> Thanks!
>
> Thomas
> --
> Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
> Embedded Linux and Kernel engineering
> https://bootlin.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20180508/877c8506/attachment.html>

  reply	other threads:[~2018-05-08  3:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-07 20:26 [Buildroot] [PATCH v2 1/1] zeromq: check if -latomic is needed Asaf Kahlon
2018-05-07 21:24 ` Thomas Petazzoni
2018-05-08  3:46   ` Asaf Kahlon [this message]
2018-05-08 13:00 ` 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='CALFsTFV4MUFtydH3nC2M=h5W+3bn+gp54MAciwOzGKEvddym8g@mail.gmail.com' \
    --to=asafka7@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.