From: "Marek Behún" <marek.behun@nic.cz>
To: "Pali Rohár" <pali@kernel.org>
Cc: Stefan Roese <sr@denx.de>, u-boot@lists.denx.de
Subject: Re: [PATCH 1/4] board: turris: Move Turris Atsha OTP code to separate file
Date: Fri, 8 Apr 2022 19:45:19 +0200 [thread overview]
Message-ID: <20220408194519.07188e90@thinkpad> (raw)
In-Reply-To: <20220408143015.23163-1-pali@kernel.org>
On Fri, 8 Apr 2022 16:30:12 +0200
Pali Rohár <pali@kernel.org> wrote:
> OTP code is not Atsha generic but also it is not Omnia specific. It is
> common for all Turris routers which use Atsha cryptochip for storing OTP.
> So move this common Turris specific Atsha OTP code from Turris Omnia into
> separate file. It will be used also by other Turris routers.
>
> Signed-off-by: Pali Rohár <pali@kernel.org>
Reviewed-by: Marek Behún <marek.behun@nic.cz>
next prev parent reply other threads:[~2022-04-08 17:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 14:30 [PATCH 1/4] board: turris: Move Turris Atsha OTP code to separate file Pali Rohár
2022-04-08 14:30 ` [PATCH 2/4] board: turris: Do not cache Atsha device in BSS Pali Rohár
2022-04-08 17:45 ` Marek Behún
2022-04-21 14:14 ` Stefan Roese
2022-04-08 14:30 ` [PATCH 3/4] board: turris: Allow to specify first eth idx of first MAC address Pali Rohár
2022-04-08 17:45 ` Marek Behún
2022-04-21 14:15 ` Stefan Roese
2022-04-08 14:30 ` [PATCH 4/4] board: turris: Rename atsha204a@64 DT node to crypto@64 Pali Rohár
2022-04-08 17:46 ` Marek Behún
2022-04-21 14:15 ` Stefan Roese
2022-04-08 17:45 ` Marek Behún [this message]
2022-04-21 14:14 ` [PATCH 1/4] board: turris: Move Turris Atsha OTP code to separate file Stefan Roese
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=20220408194519.07188e90@thinkpad \
--to=marek.behun@nic.cz \
--cc=pali@kernel.org \
--cc=sr@denx.de \
--cc=u-boot@lists.denx.de \
/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