From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] imx-mkimage: Add patch to satisfy unused version generation
Date: Wed, 27 Feb 2019 18:21:23 +0100 [thread overview]
Message-ID: <20190227182123.706da2b1@windsurf> (raw)
In-Reply-To: <20190225212359.19095-1-nerv@dawncrow.de>
Hello Andr?,
On Mon, 25 Feb 2019 22:23:59 +0100
Andr? Hentschel <nerv@dawncrow.de> wrote:
> Fixes:
>
> http://autobuild.buildroot.net/results/1973d39b113c37e65c35f1f0a56354f192ae02d7
>
> Signed-off-by: Andr? Hentschel <nerv@dawncrow.de>
> ---
> .../0003-Add-unused-fake-version.patch | 32 +++++++++++++++++++
> 1 file changed, 32 insertions(+)
> create mode 100644 package/imx-mkimage/0003-Add-unused-fake-version.patch
Applied to next, thanks. I assumed this patch was for next, as the
build failure is on next, and I suppose is related to the recent bump
of imx-mkimage.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-02-27 17:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 21:23 [Buildroot] [PATCH 1/1] imx-mkimage: Add patch to satisfy unused version generation André Hentschel
2019-02-27 17:21 ` 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=20190227182123.706da2b1@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