All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	 conor+dt@kernel.org, michal.simek@amd.com,
	devicetree@vger.kernel.org,
	 linux-arm-kernel@lists.infradead.org,
	 Praveen Teja Kundanala <praveen.teja.kundanala@amd.com>
Cc: linux-kernel@vger.kernel.org-, praveent@amd.com
Subject: Re: (subset) [PATCH V3 0/3] Add ZynqMP efuse access support
Date: Sat, 27 Jan 2024 11:43:36 +0000	[thread overview]
Message-ID: <170635581622.41421.8980881999042944764.b4-ty@linaro.org> (raw)
In-Reply-To: <20240108052617.32510-1-praveen.teja.kundanala@amd.com>


On Mon, 08 Jan 2024 10:56:14 +0530, Praveen Teja Kundanala wrote:
> Add following support
>  - ZynqMP efuse firmware API for efuse access
>  - Convert txt to yaml file
>  - Update driver to provide support to
>     read/write ZynqMP efuse memory
> 
> The first patch depends on
> https://lore.kernel.org/linux-arm-kernel/20231004094116.27128-2-jay.buddhabhatti@amd.com/
> please consider applying these patches accordingly.
> 
> [...]

Applied, thanks!

[2/3] dt-bindings: nvmem: Convert xlnx,zynqmp-nvmem.txt to yaml
      commit: a0cfd5e997824d0bd8c7620d40cdb324121a2fc7

Best regards,
-- 
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>


WARNING: multiple messages have this Message-ID (diff)
From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	 conor+dt@kernel.org, michal.simek@amd.com,
	devicetree@vger.kernel.org,
	 linux-arm-kernel@lists.infradead.org,
	 Praveen Teja Kundanala <praveen.teja.kundanala@amd.com>
Cc: linux-kernel@vger.kernel.org-, praveent@amd.com
Subject: Re: (subset) [PATCH V3 0/3] Add ZynqMP efuse access support
Date: Sat, 27 Jan 2024 11:43:36 +0000	[thread overview]
Message-ID: <170635581622.41421.8980881999042944764.b4-ty@linaro.org> (raw)
In-Reply-To: <20240108052617.32510-1-praveen.teja.kundanala@amd.com>


On Mon, 08 Jan 2024 10:56:14 +0530, Praveen Teja Kundanala wrote:
> Add following support
>  - ZynqMP efuse firmware API for efuse access
>  - Convert txt to yaml file
>  - Update driver to provide support to
>     read/write ZynqMP efuse memory
> 
> The first patch depends on
> https://lore.kernel.org/linux-arm-kernel/20231004094116.27128-2-jay.buddhabhatti@amd.com/
> please consider applying these patches accordingly.
> 
> [...]

Applied, thanks!

[2/3] dt-bindings: nvmem: Convert xlnx,zynqmp-nvmem.txt to yaml
      commit: a0cfd5e997824d0bd8c7620d40cdb324121a2fc7

Best regards,
-- 
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2024-01-27 11:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-08  5:26 [PATCH V3 0/3] Add ZynqMP efuse access support Praveen Teja Kundanala
2024-01-08  5:26 ` Praveen Teja Kundanala
2024-01-08  5:26 ` [PATCH V3 1/3] firmware: xilinx: Add ZynqMP efuse access API Praveen Teja Kundanala
2024-01-08  5:26   ` Praveen Teja Kundanala
2024-01-08  8:16   ` Michal Simek
2024-01-08  8:16     ` Michal Simek
2024-01-29  7:20   ` Michal Simek
2024-01-29  7:20     ` Michal Simek
2024-01-08  5:26 ` [PATCH V3 2/3] dt-bindings: nvmem: Convert xlnx,zynqmp-nvmem.txt to yaml Praveen Teja Kundanala
2024-01-08  5:26   ` Praveen Teja Kundanala
2024-01-08  7:08   ` Krzysztof Kozlowski
2024-01-08  7:08     ` Krzysztof Kozlowski
2024-01-08 10:19     ` Kundanala, Praveen Teja
2024-01-08 10:19       ` Kundanala, Praveen Teja
2024-01-08  5:26 ` [PATCH V3 3/3] nvmem: zynqmp_nvmem: Add support to access efuse Praveen Teja Kundanala
2024-01-08  5:26   ` Praveen Teja Kundanala
2024-01-27 11:42   ` Srinivas Kandagatla
2024-01-27 11:42     ` Srinivas Kandagatla
2024-01-27 11:43 ` Srinivas Kandagatla [this message]
2024-01-27 11:43   ` (subset) [PATCH V3 0/3] Add ZynqMP efuse access support Srinivas Kandagatla

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=170635581622.41421.8980881999042944764.b4-ty@linaro.org \
    --to=srinivas.kandagatla@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org- \
    --cc=michal.simek@amd.com \
    --cc=praveen.teja.kundanala@amd.com \
    --cc=praveent@amd.com \
    --cc=robh+dt@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.