From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/2] mtd: bump to version 2.0.0
Date: Tue, 20 Jun 2017 22:33:13 +0200 [thread overview]
Message-ID: <20170620223313.2fe37c1d@windsurf.lan> (raw)
In-Reply-To: <1496955910-32315-1-git-send-email-thomas.petazzoni@free-electrons.com>
Hello,
On Thu, 8 Jun 2017 23:05:08 +0200, Thomas Petazzoni wrote:
> From: Adam Duskett <Aduskett@gmail.com>
>
> MTD Tools was bumped to version 2.0 after over a decade of being at
> 1.5.2.
>
> This revision includes:
> - Moving from a handwritten makefile to autotools.
> - Restructuring and cleaning up the source tree.
> - Fixing the problems that the patches in the package/mtd directory fixed.
>
> Changes:
> - Move from generic-package to autotools-package in mtd.mk.
> - Remove no longer necessary patches.
> - Update binary locations in mtd.mk
> - Update library/header locations in mtd.mk
> - Remove MTD_ADD_MISSING_LINTL definition from mtd.mk, as it's no longer
> needed.
>
> Tested with toolchains compiled with musl, uclibc, and glibc.
>
> Signed-off-by: Adam Duskett <aduskett@codeblue.com>
[snip]
I've applied both patches to master. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-06-20 20:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 21:05 [Buildroot] [PATCH v2 1/2] mtd: bump to version 2.0.0 Thomas Petazzoni
2017-06-08 21:05 ` [Buildroot] [PATCH v2 2/2] mtd: switch to a foreach loop for installation Thomas Petazzoni
2017-06-09 3:00 ` [Buildroot] [PATCH v2 1/2] mtd: bump to version 2.0.0 Baruch Siach
2017-06-20 20:33 ` Thomas Petazzoni
2017-06-20 20:33 ` 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=20170620223313.2fe37c1d@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 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.