From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] imx-uuc: bump revision to 79e9798e
Date: Tue, 13 Nov 2018 22:08:10 +0100 [thread overview]
Message-ID: <20181113220810.3f4c3cba@windsurf> (raw)
In-Reply-To: <20181112094402.1815-1-gary.bisson@boundarydevices.com>
Hello Gary,
On Mon, 12 Nov 2018 10:44:02 +0100, Gary Bisson wrote:
> Main changes:
> - fix build error by gcc 8.2
I know it is what the upstream commit says, but the makedev() issue has
nothing to do with gcc 8.2, but with glibc 2.28. I fixed up the commit
log on that aspect.
To be honest, I hesitated a bit because we normally don't take version
bumps in master at this point. However, this is a fairly small
and not that widely used package, the number of upstream changes is not
enormous, so I applied it to master. But I really hesitated with asking
for just a backport of the glibc 2.28 fix instead.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-11-13 21:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 9:44 [Buildroot] [PATCH] imx-uuc: bump revision to 79e9798e Gary Bisson
2018-11-13 21:08 ` Thomas Petazzoni [this message]
2018-11-14 9:29 ` Gary Bisson
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=20181113220810.3f4c3cba@windsurf \
--to=thomas.petazzoni@bootlin.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