From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 0/3] efibootmgr: build with uClibc
Date: Mon, 28 Nov 2016 21:14:11 +0100 [thread overview]
Message-ID: <20161128211411.28555fc5@free-electrons.com> (raw)
In-Reply-To: <20161128163553.173811-1-andriy.shevchenko@linux.intel.com>
Hello,
On Mon, 28 Nov 2016 18:35:50 +0200, Andy Shevchenko wrote:
> These patches make possible to use efibootmgr with uClibc. All patches had been
> sent to upstream.
>
> I have tested in my environment that doesn't use unicode characters. So, any
> additional tests are appreciated.
>
> Andy Shevchenko (3):
> efivar: bump to version 30
> efivar: allow build with uClibc
> efibootmrg: Allow build with uClibc
Why did you resend those patches? You already sent them yesterday, and
I already applied them to our next branch. I even made some comments,
which are anyway not taken into account in this new iteration.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-11-28 20:14 UTC|newest]
Thread overview: 10+ 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
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 ` Thomas Petazzoni [this message]
2016-12-13 11:37 ` [Buildroot] [PATCH v1 0/3] efibootmgr: " Andy Shevchenko
-- strict thread matches above, loose matches on Subject: below --
2016-11-27 14:32 Andy Shevchenko
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=20161128211411.28555fc5@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