<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-xilinx.git/meta-microblaze/recipes-devtools/m4/files/m4-stack-direction-microblaze.patch, branch scarthgap</title>
<subtitle>Mirror of git.yoctoproject.org/meta-xilinx.git</subtitle>
<id>https://git.enea.com/cgit/linux/meta-xilinx.git/atom?h=scarthgap</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-xilinx.git/atom?h=scarthgap'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-xilinx.git/'/>
<updated>2023-07-21T20:39:34+00:00</updated>
<entry>
<title>meta-microblaze: YP now requires Upstream-Status in patches</title>
<updated>2023-07-21T20:39:34+00:00</updated>
<author>
<name>Mark Hatle</name>
<email>mark.hatle@amd.com</email>
</author>
<published>2023-07-21T20:35:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-xilinx.git/commit/?id=c81d3b5014d43aa881b24e38200ed88652ea36ac'/>
<id>urn:sha1:c81d3b5014d43aa881b24e38200ed88652ea36ac</id>
<content type='text'>
Signed-off-By line is also required and added where missing.

Signed-off-by: Mark Hatle &lt;mark.hatle@amd.com&gt;
</content>
</entry>
<entry>
<title>microblaze m4/diffutils/grep: Add stack direction info to m4 macros</title>
<updated>2022-01-14T19:21:55+00:00</updated>
<author>
<name>Mark Hatle</name>
<email>mark.hatle@xilinx.com</email>
</author>
<published>2021-12-02T12:39:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-xilinx.git/commit/?id=c9afc4648479ca31bacfd1d814689794988ea5d9'/>
<id>urn:sha1:c9afc4648479ca31bacfd1d814689794988ea5d9</id>
<content type='text'>
These tools require knowledge of the stack direction, since we are cross
compiling they are unable to detect the stack growth direction so it must
be defined in the m4 macro.

It turns out the direction was already set, but defined as
'microblaze' instead of 'microblaze*' which caused problems on little
endian.

Signed-off-by: Mark Hatle &lt;mark.hatle@xilinx.com&gt;
</content>
</entry>
</feed>
