From: Michal Simek <michal.simek@amd.com>
To: Jay Buddhabhatti <jay.buddhabhatti@amd.com>,
gregkh@linuxfoundation.org, sai.krishna.potthuri@amd.com,
linus.walleij@linaro.org, nava.kishore.manne@amd.com,
dhaval.r.shah@amd.com, robh@kernel.org, marex@denx.de,
roman.gushchin@linux.dev, arnd@arndb.de,
shubhrajyoti.datta@amd.com
Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] add platform check in event manager driver
Date: Mon, 18 Dec 2023 11:56:43 +0100 [thread overview]
Message-ID: <d07b5884-c7c1-482a-a911-a0b7a75100d3@amd.com> (raw)
In-Reply-To: <20231218094009.13528-1-jay.buddhabhatti@amd.com>
On 12/18/23 10:40, Jay Buddhabhatti wrote:
> Some error event IDs for Versal and Versal NET are different.
> Both the platforms should access their respective error event
> IDs so use sub_family_code to check for Versal or Versal NET
> platform and check error IDs for respective platforms.
>
> Jay Buddhabhatti (2):
> firmware: xilinx: Export function to use in other module
> drivers: soc: xilinx: add check for platform
>
> drivers/firmware/xilinx/zynqmp.c | 3 ++-
> drivers/soc/xilinx/xlnx_event_manager.c | 25 ++++++++++++++++++++-----
> include/linux/firmware/xlnx-zynqmp.h | 22 ++++++++++++++++++----
> 3 files changed, 40 insertions(+), 10 deletions(-)
>
Acked-by: Michal Simek <michal.simek@amd.com>
Thanks,
Michal
prev parent reply other threads:[~2023-12-18 10:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 9:40 Jay Buddhabhatti
2023-12-18 9:40 ` [PATCH 1/2] firmware: xilinx: Export function to use in other module Jay Buddhabhatti
2023-12-18 9:40 ` [PATCH 2/2] drivers: soc: xilinx: add check for platform Jay Buddhabhatti
2023-12-18 10:56 ` Michal Simek [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=d07b5884-c7c1-482a-a911-a0b7a75100d3@amd.com \
--to=michal.simek@amd.com \
--cc=arnd@arndb.de \
--cc=dhaval.r.shah@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=jay.buddhabhatti@amd.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=nava.kishore.manne@amd.com \
--cc=robh@kernel.org \
--cc=roman.gushchin@linux.dev \
--cc=sai.krishna.potthuri@amd.com \
--cc=shubhrajyoti.datta@amd.com \
/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
all inboxes | Powered by JetHome®