From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, v1, 3/4] env: add a version number to check API
Date: Fri, 14 Apr 2017 17:09:24 -0400 [thread overview]
Message-ID: <20170414210924.GD19897@bill-the-cat> (raw)
In-Reply-To: <1491408483-13228-4-git-send-email-sbabic@denx.de>
On Wed, Apr 05, 2017 at 06:08:02PM +0200, Stefano Babic wrote:
> Changes in the environment library are difficult to tracked by programs
> using the library. Add simply an API version number that must be
> increased each time when the API is changed.
>
> This can be detected and a program can work with different versions of
> the library.
>
> Signed-off-by: Stefano Babic <sbabic@denx.de>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170414/417c369d/attachment.sig>
next prev parent reply other threads:[~2017-04-14 21:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 16:07 [U-Boot] [PATCH v1 0/4] env tools fixes Stefano Babic
2017-04-05 16:08 ` [U-Boot] [PATCH v1 1/4] Rename aes.h to uboot_aes.h Stefano Babic
2017-04-14 21:09 ` [U-Boot] [U-Boot,v1,1/4] " Tom Rini
2017-04-05 16:08 ` [U-Boot] [PATCH v1 2/4] env: split fw_env.h in public and private parts Stefano Babic
2017-04-14 21:09 ` [U-Boot] [U-Boot, v1, " Tom Rini
2017-04-05 16:08 ` [U-Boot] [PATCH v1 3/4] env: add a version number to check API Stefano Babic
2017-04-14 21:09 ` Tom Rini [this message]
2017-04-05 16:08 ` [U-Boot] [PATCH v1 4/4] env: fix memory leak in fw_env routines Stefano Babic
2017-04-14 21:09 ` [U-Boot] [U-Boot, v1, " Tom Rini
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=20170414210924.GD19897@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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.