From: Sudeep Holla <sudeep.holla@arm.com>
To: Peng Fan <peng.fan@oss.nxp.com>
Cc: Peng Fan <peng.fan@nxp.com>,
Cristian Marussi <cristian.marussi@arm.com>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
arm-scmi@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] firmware: arm_scmi/imx: Support dump syslog
Date: Tue, 6 Jan 2026 15:46:29 +0000 [thread overview]
Message-ID: <aV0uVXXbxKQ5qzLD@bogus> (raw)
In-Reply-To: <aVuzVNmG2l-igiEB@nxa18884-linux.ap.freescale.net>
On Mon, Jan 05, 2026 at 08:49:24PM +0800, Peng Fan wrote:
> Hi Sudeep,
>
> Hope you're doing well. Apologies for following up again, but this v3 patchset
> has been pending for quite some time. I wanted to check if everything looks
> good on your end.
>
Yes overall it looks good to me.
> Could you please confirm whether you plan to pick both patches?
As I had asked once in previous version, I need i.MX maintainer ACK to pick
it up myself.
> Or do you need an A-b from the i.MX maintainer for patch 2?
Yes as mentioned above.
> Alternatively, I can ask Shawn to pick patch 2 if you only intend to take patch 1.
I think that would break build or need to wait for another cycle.
I can ack if it can be routed via i.MX tree or need ACK to pick it up myself.
--
Regards,
Sudeep
next prev parent reply other threads:[~2026-01-06 15:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 12:07 [PATCH v3 0/2] firmware: arm_scmi/imx: Support dump syslog Peng Fan
2025-10-29 12:07 ` [PATCH v3 1/2] firmware: arm_scmi: imx: Support getting syslog of MISC protocol Peng Fan
2026-01-06 15:49 ` Sudeep Holla
2025-10-29 12:07 ` [PATCH v3 2/2] firmware: imx: sm-misc: Dump syslog info Peng Fan
2025-12-16 1:16 ` [PATCH v3 0/2] firmware: arm_scmi/imx: Support dump syslog Peng Fan
2026-01-05 12:49 ` Peng Fan
2026-01-06 15:46 ` Sudeep Holla [this message]
2026-01-07 1:34 ` Peng Fan
2026-01-12 11:59 ` Sudeep Holla
2026-01-17 2:34 ` Shawn Guo
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=aV0uVXXbxKQ5qzLD@bogus \
--to=sudeep.holla@arm.com \
--cc=arm-scmi@vger.kernel.org \
--cc=cristian.marussi@arm.com \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox