<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<pre>
</pre>
<div class="moz-cite-prefix">On 2020-09-23 17:05, Gedare Bloom
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAC82fA3m88PMYJNADVJw-fmt77kr-N1bKjCwL4xKnAt3kBXEZg@mail.gmail.com">
<pre class="moz-quote-pre" wrap="">On Wed, Sep 23, 2020 at 4:34 AM Daniel Hellstrom <a class="moz-txt-link-rfc2396E" href="mailto:daniel@gaisler.com"><daniel@gaisler.com></a> wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">
Hi Sebastian,
Thanks for asking and sorry for dropping the ball on these.
The status is that two needs updating (BSD license for new CAN files and
the last tn0018 patch needs some redesign based on feedback) and the
others are accepted for master. I've sent an response on the tn0018
errata patch just now. I would like to push them on the 5 and master
branches. To get them onto 5, should I create a ticket for the whole
patch set? I will try getting this done next next couple of days, and
have a look at you patches too, thanks!
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
It would be good to separate them logically to the TN-0018 errata
fixes vs the CAN/grlib improvements. The concern for pushing them to 5
is that they touch core sparc files, but since you guys are releasing
them this way in RCC I'm also comfortable with it. I didn't see any
changes outside the sparc (since currently grlib is sparc-specific
too). We'll need those tickets to help us with the dot-release notes.</pre>
</blockquote>
<p>Sorry for my very late response. There were some more updates on
a few of the patches based on the review comments which has been
addressed. I have now created tickets for all of them which are
referenced from the patches, so I will go ahead and push them for
the 5-branch (the posted patches targeted 5).</p>
<p> However, I will wait with the TN-0018 before I get an
acknowledge for that one. I updated the its ticket with links to
the GCC patch that has now been accepted into upstreams GCC
(GCC-10 stable and master). The TN0018 patch is not enabled if the
GCC-patch is not included in the toolchain, so I believe it should
be ok to push, even before RSB is updated?<br>
</p>
<p> <a class="moz-txt-link-freetext" href="https://devel.rtems.org/ticket/4155">https://devel.rtems.org/ticket/4155</a><br>
</p>
<p>Next step for me is to add some configurations for the new build
system before I can push them to RTEMS/master.</p>
<p>Thanks,<br>
/Daniel<br>
</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:CAC82fA3m88PMYJNADVJw-fmt77kr-N1bKjCwL4xKnAt3kBXEZg@mail.gmail.com">
<pre class="moz-quote-pre" wrap="">
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Kind Regards,
Daniel
On 2020-09-18 10:03, Sebastian Huber wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Hallo Daniel,
what are your plans with respect to this patch set?
Please also have a look at:
<a class="moz-txt-link-freetext" href="https://lists.rtems.org/pipermail/devel/2020-September/062176.html">https://lists.rtems.org/pipermail/devel/2020-September/062176.html</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">_______________________________________________
devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:devel@rtems.org">devel@rtems.org</a>
<a class="moz-txt-link-freetext" href="http://lists.rtems.org/mailman/listinfo/devel">http://lists.rtems.org/mailman/listinfo/devel</a>
</pre>
</blockquote>
</blockquote>
</body>
</html>