From: Jonatan Hatakeyama Zeidler <jonatan.zeidler@brainlab.com>
To: buildroot@busybox.net
Subject: [Buildroot] Fix OpTee PyCryptodomex Python 2 vs 3 issue
Date: Fri, 7 Aug 2020 07:12:02 +0000 [thread overview]
Message-ID: <2c647da9-72e5-ec1c-3167-ea7c90081ddb@brainlab.com> (raw)
In-Reply-To: <20200806214335.2a8ccd2f@windsurf.home>
Hello Thomas,
On 06.08.20 21:43, Thomas Petazzoni wrote:
>
> I haven't reviewed your patch, nor the patch series I will point, but I
> believe the patch series at:
>
> https://patchwork.ozlabs.org/project/buildroot/list/?series=191437
>
> should address this issue.
this addresses the same issue indeed. Is there anything I can do to help
get that merged?
Best regards
Jonatan
--
Jonatan Hatakeyama Zeidler
Software Engineer
Brainlab Robotics
T +49 89 99 15 68 ? 0
F +49 89 99 15 68 ? 5033
Medineering GmbH
Olof-Palme-Str. 1, 81829 M?nchen, Germany
Sitz d. Gesellschaft: M?nchen - Handelsregister: M?nchen HRB 212991
VAT.: DE296021936
Managing Director: Dr.-Ing. Maximilian Krinninger, Dr.-Ing. Stephan Nowatschin
This email, including its attachments, is intended only for the confidential use of the individual to whom it is addressed. If you are not the intended recipient, any use, dissemination, distribution or copying of this message or its attachments is prohibited. If you have received this message in error, please notify us immediately, and delete this message and its attachments permanently from your system.
prev parent reply other threads:[~2020-08-07 7:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 9:30 [Buildroot] Fix OpTee PyCryptodomex Python 2 vs 3 issue Jonatan Hatakeyama Zeidler
2020-08-06 19:43 ` Thomas Petazzoni
2020-08-07 7:12 ` Jonatan Hatakeyama Zeidler [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=2c647da9-72e5-ec1c-3167-ea7c90081ddb@brainlab.com \
--to=jonatan.zeidler@brainlab.com \
--cc=buildroot@busybox.net \
/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