From: Sudeep Holla <sudeep.holla@arm.com>
To: Peng Fan <peng.fan@oss.nxp.com>
Cc: Shawn Guo <shawnguo@kernel.org>, Peng Fan <peng.fan@nxp.com>,
Cristian Marussi <cristian.marussi@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
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: Mon, 12 Jan 2026 11:59:07 +0000 [thread overview]
Message-ID: <aWTiC78PXRoadeJy@bogus> (raw)
In-Reply-To: <aV24N72FoGeGwgqm@shlinux89>
On Wed, Jan 07, 2026 at 09:34:47AM +0800, Peng Fan wrote:
> On Tue, Jan 06, 2026 at 03:46:29PM +0000, Sudeep Holla wrote:
> >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.
>
> Thanks a lot.
>
> >
> ...
> >> 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.
>
> Shawn,
>
> Do you plan to pick the two patches with Sudeep's Ack in patch 1? Or
> you prefer to route the patches via SCMI tree with your Ack?
I noticed this morning we are already at -rc5, which is later than my usual PR
timing (I generally aim to send to the SoC team between -rc4 and -rc5). I have
already sent the SCMI PR.
For these changes, would it be acceptable to route them via the i.MX tree if
they are still intended for v7.0/v6.20? If not, I am happy to defer and pick
them up for the merge window after next.
--
Regards,
Sudeep
next prev parent reply other threads:[~2026-01-12 11:59 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
2026-01-07 1:34 ` Peng Fan
2026-01-12 11:59 ` Sudeep Holla [this message]
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=aWTiC78PXRoadeJy@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 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.