From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] efivar: bump to version 31
Date: Tue, 11 Jul 2017 18:25:54 +0200 [thread overview]
Message-ID: <20170711182554.7677e18e@windsurf.lan> (raw)
In-Reply-To: <20170711161054.qhsr2glldmil6uzt@tarshish>
Hello,
On Tue, 11 Jul 2017 19:10:54 +0300, Baruch Siach wrote:
> On Tue, Jul 11, 2017 at 05:59:56PM +0200, Thomas Petazzoni wrote:
> > This allows to drop two patches that have been upstreamed:
> >
> > 0001-Use-z-muldefs-to-avoid-the-multiple-definitions-bug-.patch is
> > upstream as of commit 18b9b3dd7ebf23a16de07b3fb6ae622be488d712
> >
> > 0003-Remove-some-extra-const-that-gcc-complains-about.patch is
> > upstream as of commit 1c7c0f71c9d22efda4156881eb187b8c69d1cca7.
>
> Version 31 is marked as pre-release[1], like 29 and 25 before. It seems like
> only even version numbers are stable releases.
OK, good point, I didn't notice that. So it was really a good idea to
split PATCH 1/3 that adds just the gcc 7.x fix from the rest of the
series.
I'll apply PATCH 1/3 and reject PATCH 2/3 and 3/3. Is that OK for you?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-07-11 16:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 15:59 [Buildroot] [PATCH 1/3] efibootmgr: fix build with gcc 7.x Thomas Petazzoni
2017-07-11 15:59 ` [Buildroot] [PATCH 2/3] efivar: bump to version 31 Thomas Petazzoni
2017-07-11 16:10 ` Baruch Siach
2017-07-11 16:25 ` Thomas Petazzoni [this message]
2017-07-11 20:47 ` Baruch Siach
2017-07-11 15:59 ` [Buildroot] [PATCH 3/3] efibootmgr: bump to version 15 Thomas Petazzoni
2017-07-22 21:21 ` [Buildroot] [PATCH 1/3] efibootmgr: fix build with gcc 7.x Thomas Petazzoni
2017-07-25 22:11 ` Peter Korsgaard
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=20170711182554.7677e18e@windsurf.lan \
--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