All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 1/3] efivar: bump to version 30
Date: Sat, 3 Dec 2016 14:34:05 +0100	[thread overview]
Message-ID: <20161203143405.0e4a8a54@free-electrons.com> (raw)
In-Reply-To: <20161128163553.173811-2-andriy.shevchenko@linux.intel.com>

Hello,

On Mon, 28 Nov 2016 18:35:51 +0200, Andy Shevchenko wrote:
> Use newest release.
> 
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

This update is causing a large number of build failures, see:

   http://autobuild.buildroot.net/?reason=efivar-30

Could you have a look?

Thanks a lot,

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

  reply	other threads:[~2016-12-03 13:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-28 16:35 [Buildroot] [PATCH v1 0/3] efibootmgr: build with uClibc Andy Shevchenko
2016-11-28 16:35 ` [Buildroot] [PATCH v1 1/3] efivar: bump to version 30 Andy Shevchenko
2016-12-03 13:34   ` Thomas Petazzoni [this message]
2016-12-03 15:18     ` Erico Nunes
2016-12-03 15:34       ` Thomas Petazzoni
2016-11-28 16:35 ` [Buildroot] [PATCH v1 2/3] efivar: allow build with uClibc Andy Shevchenko
2016-11-28 16:35 ` [Buildroot] [PATCH v1 3/3] efibootmrg: Allow " Andy Shevchenko
2016-11-28 20:14 ` [Buildroot] [PATCH v1 0/3] efibootmgr: " Thomas Petazzoni
2016-12-13 11:37   ` Andy Shevchenko
  -- strict thread matches above, loose matches on Subject: below --
2016-11-27 14:32 Andy Shevchenko
2016-11-27 14:32 ` [Buildroot] [PATCH v1 1/3] efivar: bump to version 30 Andy Shevchenko
2016-11-27 15:48   ` 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=20161203143405.0e4a8a54@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 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.