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] [autobuild] package/nbd: fix static builds
Date: Tue, 18 Aug 2015 11:46:55 +0200	[thread overview]
Message-ID: <20150818114655.39251af2@free-electrons.com> (raw)
In-Reply-To: <20150818093230.GA3799@free.fr>

Dear Yann E. MORIN,

On Tue, 18 Aug 2015 11:32:30 +0200, Yann E. MORIN wrote:

> > > +Upstream status: hack, not submitted.
> > 
> > Please submit the patch upstream anyway, so that upstream is aware of
> > the problem, and hopefully implements a proper solution.
> 
> I'm doing a proper patch for upstream, that does the rename globally,
> and that's what I'm gonna submit.

Perfect, thanks.

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

      reply	other threads:[~2015-08-18  9:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-13 19:55 [Buildroot] [PATCH] [autobuild] package/nbd: fix static builds Yann E. MORIN
2015-08-18  9:18 ` Thomas Petazzoni
2015-08-18  9:32   ` Yann E. MORIN
2015-08-18  9:46     ` 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=20150818114655.39251af2@free-electrons.com \
    --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