From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Pavel Kozlov <Pavel.Kozlov@synopsys.com>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Cc: "linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
Vineet Gupta <vineet.gupta@linux.dev>
Subject: Re: Pavel new maintainer of ARC port
Date: Wed, 22 Feb 2023 14:52:11 -0300 [thread overview]
Message-ID: <9f959842-ced5-327b-5893-829019bfc205@linaro.org> (raw)
In-Reply-To: <816b6a43-6b23-cfd7-266f-e65b8830b542@linaro.org>
On 21/02/23 15:59, Adhemerval Zanella Netto wrote:
>
>
> On 21/02/23 10:55, Pavel Kozlov via Libc-alpha wrote:
>> Hi all,
>>
>> I'm excited to introduce myself and become a part of the community.
>>
>> I'm a software engineer in Synopsys and member of a team working to enhance
>> support for ARC CPUs in the GNU Linux ecosystem.
>>
>> I would appreciate any guidance or advice on how I can get involved and
>> contribute to the community. I'm always looking for opportunities to connect
>> with other developers and learn from their experiences.
>>
>> As a final step of setup, I've updated wiki and added myself as ARC
>> maintainer. Also, thanks Carlos, for help with my setup.
>>
>> Best regards,
>> Pavel Kozlov
>
> Hi Pavel,
>
> Carlos might already brought to your attention, but we have a weekly
> call [1] where we discuss the current patchwork status [2], any blocker
> someone might have, future work, or to discuss bug report or any other
> issue. So fell free to hop in if you have anything to discuss.
>
> [1] https://sourceware.org/glibc/wiki/PatchworkReviewMeetings
> [2] https://patchwork.sourceware.org/project/glibc/list/
Another thing you might want to check is to do some triage on the
ARC failures reported by on the 2.37 release page. Some might be
just due timeout issues (test taking to long), however some might
require some work (the test-float64-trunc for instance).
prev parent reply other threads:[~2023-02-22 17:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 13:55 Pavel Kozlov
2023-02-21 18:59 ` Adhemerval Zanella Netto
2023-02-22 17:52 ` Adhemerval Zanella Netto [this message]
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=9f959842-ced5-327b-5893-829019bfc205@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=Pavel.Kozlov@synopsys.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=vineet.gupta@linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).