<feed xmlns='http://www.w3.org/2005/Atom'>
<title>buildroot/package/devmem2/devmem2.hash, branch 2018.02</title>
<subtitle>OpenPOWER buildroot sources</subtitle>
<id>https://git.raptorcs.com/git/buildroot/atom?h=2018.02</id>
<link rel='self' href='https://git.raptorcs.com/git/buildroot/atom?h=2018.02'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/'/>
<updated>2017-07-03T22:04:55+00:00</updated>
<entry>
<title>package/devmem2: fix legal-info</title>
<updated>2017-07-03T22:04:55+00:00</updated>
<author>
<name>Peter Korsgaard</name>
<email>peter@korsgaard.com</email>
</author>
<published>2017-07-03T22:04:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=a1b630779f78e0413d8d70ffcc209e412c9f887f'/>
<id>urn:sha1:a1b630779f78e0413d8d70ffcc209e412c9f887f</id>
<content type='text'>
Fixes:
http://autobuild.buildroot.net/results/1c6/1c69c77d7b378f6f76790fb5ca0078d0db0c40f8

devmem2 is a single C file that is downloaded as-is, and we patch it.
We also use that file as the license file.

Thus, the file when it is downloaded has a specific hash, but when
saved by legal-info, it has a different hash.

However, we can't store two different hashes for the same _filename_
with different content.

So, we extract the license file as a pre-patch hook, and store it in a
separate file, for which we can now add a hash.

Signed-off-by: Peter Korsgaard &lt;peter@korsgaard.com&gt;
</content>
</entry>
<entry>
<title>devmem2: add a hash file</title>
<updated>2015-10-04T16:36:28+00:00</updated>
<author>
<name>Vicente Olivert Riera</name>
<email>Vincent.Riera@imgtec.com</email>
</author>
<published>2015-10-04T16:24:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=5bc76921fa99c0c87486de53c617587508fe01a4'/>
<id>urn:sha1:5bc76921fa99c0c87486de53c617587508fe01a4</id>
<content type='text'>
Signed-off-by: Vicente Olivert Riera &lt;Vincent.Riera@imgtec.com&gt;
Signed-off-by: Peter Korsgaard &lt;peter@korsgaard.com&gt;
</content>
</entry>
</feed>
