<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm63xx/u-boot/tools/env, branch master</title>
<subtitle>Broadcom-s U-Boot</subtitle>
<id>https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/atom?h=master</id>
<link rel='self' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/'/>
<updated>2019-06-20T14:57:08Z</updated>
<entry>
<title>fw_env: Add missing write failure check</title>
<updated>2019-06-20T14:57:08Z</updated>
<author>
<name>Alex Kiernan</name>
</author>
<published>2019-06-12T14:27:55Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=a762311a6cf02396977f59babdf945c226f4404f'/>
<id>urn:sha1:a762311a6cf02396977f59babdf945c226f4404f</id>
<content type='text'>
If flash_write fails, whilst we propagate this up to our caller, we need
to avoid swapping in the new file (if we're on a filesystem) in this
case.

Fixes: dbc34323796b ("tools: env: Implement atomic replace for filesystem")
Signed-off-by: Alex Kiernan &lt;alex.kiernan@gmail.com&gt;
</content>
</entry>
<entry>
<title>env: add missing newline</title>
<updated>2019-05-05T12:48:50Z</updated>
<author>
<name>Philip Molloy</name>
</author>
<published>2019-03-31T03:44:57Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=9337a08768dfa0a006382f1d05cf69b5f67f7844'/>
<id>urn:sha1:9337a08768dfa0a006382f1d05cf69b5f67f7844</id>
<content type='text'>
Signed-off-by: Philip Molloy &lt;philip@philipmolloy.com&gt;
</content>
</entry>
<entry>
<title>fw_env: Fix double free</title>
<updated>2019-04-26T22:58:21Z</updated>
<author>
<name>Björn Stenberg</name>
</author>
<published>2019-04-17T14:56:54Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=2b4ea2b34416b892fdf54d8f334106f9bf4df8ae'/>
<id>urn:sha1:2b4ea2b34416b892fdf54d8f334106f9bf4df8ae</id>
<content type='text'>
addr0 is being freed twice, leading to segmentation fault

Signed-off-by: Björn Stenberg &lt;bjorn@haxx.se&gt;
</content>
</entry>
<entry>
<title>include/version.h: workaround sysroot inc order</title>
<updated>2018-09-11T00:20:34Z</updated>
<author>
<name>Matt Weber</name>
</author>
<published>2018-07-27T03:37:53Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=e1df3fa364a5f0d8b4c589c29c0f304d69a0121c'/>
<id>urn:sha1:e1df3fa364a5f0d8b4c589c29c0f304d69a0121c</id>
<content type='text'>
On some systems the host system or even the cross sysroot can
contain a version.h.  This leads to the wrong file being picked
up and a PLAIN_VERSION undefined error.

This workaround symlinks the version.h into the tool folder to
allow reordering of search folders.

Fixes
http://autobuild.buildroot.net/results/770/7702d5df36a6532aafdbe6e9e62709bbfa058b54/build-end.log
http://autobuild.buildroot.net/results/e34/e3401027d2fb3ce565ca9e2456a427afd3610a87/build-end.log
... additional can be found with these queries ...
http://autobuild.buildroot.net/?reason=uboot-tools-2018.03
http://autobuild.buildroot.net/?reason=uboot-tools-2018.05

Upstream: pending

Signed-off-by: Matthew Weber &lt;matthew.weber@rockwellcollins.com&gt;
</content>
</entry>
<entry>
<title>Revert "fw_printenv: Don't bail out directly after one env read error"</title>
<updated>2018-07-02T02:10:33Z</updated>
<author>
<name>Tom Rini</name>
</author>
<published>2018-07-02T02:10:33Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=168de20f3b6ccefef0ff5757fa5310f47a95c2f0'/>
<id>urn:sha1:168de20f3b6ccefef0ff5757fa5310f47a95c2f0</id>
<content type='text'>
As pointed out by Wolfgang Denk, the problem with this fix is that while
interactive users will see that we have found one part of the
environment failed and are using the other, progmatic use will not see
this and can lead to problems.

Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>fw_printenv: Don't bail out directly after one env read error</title>
<updated>2018-06-27T17:09:16Z</updated>
<author>
<name>Joe Hershberger</name>
</author>
<published>2018-06-26T09:37:59Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=3925b2ac97b50b1facab096ac98243615683c295'/>
<id>urn:sha1:3925b2ac97b50b1facab096ac98243615683c295</id>
<content type='text'>
When using a redundant environment a read error should simply mean to
not use that copy instead of giving up completely. The other copy may
be just fine.

Signed-off-by: Joe Hershberger &lt;joe.hershberger@ni.com&gt;
Signed-off-by: Ioan-Adrian Ratiu &lt;adrian.ratiu@ni.com&gt;
</content>
</entry>
<entry>
<title>u-boot: Fix several typos</title>
<updated>2018-06-13T11:49:13Z</updated>
<author>
<name>Shyam Saini</name>
</author>
<published>2018-06-07T14:17:19Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=919d25c9208d12a4fc3691972ad69ed4e40455ba'/>
<id>urn:sha1:919d25c9208d12a4fc3691972ad69ed4e40455ba</id>
<content type='text'>
's/environemnt/environment/' and
	's/Environemnt/Environment/'

Signed-off-by: Shyam Saini &lt;shyam@amarulasolutions.com&gt;
</content>
</entry>
<entry>
<title>tools: env: Use getline rather than fgets when reading config/script</title>
<updated>2018-06-13T11:49:12Z</updated>
<author>
<name>Alex Kiernan</name>
</author>
<published>2018-06-07T12:20:05Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=94b233f443456a1cb868868b3b7f6876471a2de4'/>
<id>urn:sha1:94b233f443456a1cb868868b3b7f6876471a2de4</id>
<content type='text'>
When reading the config file, or a script file, use getline rather than
fgets so line lengths aren't limited by the size of a compiled in buffer
(128 characters for config, 1024 for scripts).

Rename 'dump' to 'line' so it's clear we're working with a line of text.

Signed-off-by: Alex Kiernan &lt;alex.kiernan@gmail.com&gt;
</content>
</entry>
<entry>
<title>SPDX: Convert all of our single license tags to Linux Kernel style</title>
<updated>2018-05-07T13:34:12Z</updated>
<author>
<name>Tom Rini</name>
</author>
<published>2018-05-06T21:58:06Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=83d290c56fab2d38cd1ab4c4cc7099559c1d5046'/>
<id>urn:sha1:83d290c56fab2d38cd1ab4c4cc7099559c1d5046</id>
<content type='text'>
When U-Boot started using SPDX tags we were among the early adopters and
there weren't a lot of other examples to borrow from.  So we picked the
area of the file that usually had a full license text and replaced it
with an appropriate SPDX-License-Identifier: entry.  Since then, the
Linux Kernel has adopted SPDX tags and they place it as the very first
line in a file (except where shebangs are used, then it's second line)
and with slightly different comment styles than us.

In part due to community overlap, in part due to better tag visibility
and in part for other minor reasons, switch over to that style.

This commit changes all instances where we have a single declared
license in the tag as both the before and after are identical in tag
contents.  There's also a few places where I found we did not have a tag
and have introduced one.

Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>fw_printenv: Fix crash due to incorrect size for malloc'ed string.</title>
<updated>2018-04-10T19:19:15Z</updated>
<author>
<name>Kristian Amlie</name>
</author>
<published>2018-04-04T08:09:57Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=8a0b827b1a12cf3e224a4c083de7a1e448356a16'/>
<id>urn:sha1:8a0b827b1a12cf3e224a4c083de7a1e448356a16</id>
<content type='text'>
Using sizeof gives the size of the pointer only, not the string. This
could easily lead to crashes when using -l argument.

Signed-off-by: Kristian Amlie &lt;kristian.amlie@northern.tech&gt;
</content>
</entry>
</feed>
