From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Joshua Yeong <joshua.yeong@starfivetech.com>
Cc: Frank Li <Frank.li@nxp.com>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
"linux-i3c@lists.infradead.org" <linux-i3c@lists.infradead.org>
Subject: Re: [PATCH] i3c: don't fail if GETHDRCAP is unsupported
Date: Thu, 3 Jul 2025 08:41:51 +0200 [thread overview]
Message-ID: <aGYmL9CpZHUtEm85@shikoro> (raw)
In-Reply-To: <26c2b49b-713e-4e9c-8bf4-0ffbd0b4b050@starfivetech.com>
Hi Joshua,
> I'm use `MMC5633` to test out the HDR-DDR functionality master functionality.
> The patch can be accepted as some controller might not support HDR.
May I read this as an Acked-by? Then, I would add it when sending v2.
Happy hacking,
Wolfram
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Joshua Yeong <joshua.yeong@starfivetech.com>
Cc: Frank Li <Frank.li@nxp.com>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
"linux-i3c@lists.infradead.org" <linux-i3c@lists.infradead.org>
Subject: Re: [PATCH] i3c: don't fail if GETHDRCAP is unsupported
Date: Thu, 3 Jul 2025 08:41:51 +0200 [thread overview]
Message-ID: <aGYmL9CpZHUtEm85@shikoro> (raw)
In-Reply-To: <26c2b49b-713e-4e9c-8bf4-0ffbd0b4b050@starfivetech.com>
Hi Joshua,
> I'm use `MMC5633` to test out the HDR-DDR functionality master functionality.
> The patch can be accepted as some controller might not support HDR.
May I read this as an Acked-by? Then, I would add it when sending v2.
Happy hacking,
Wolfram
next prev parent reply other threads:[~2025-07-03 6:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 7:34 [PATCH] i3c: don't fail if GETHDRCAP is unsupported Wolfram Sang
2025-06-25 7:34 ` Wolfram Sang
2025-06-25 15:24 ` Frank Li
2025-06-25 15:24 ` Frank Li
2025-06-25 16:41 ` Wolfram Sang
2025-06-25 16:41 ` Wolfram Sang
2025-06-26 2:46 ` Joshua Yeong
2025-06-26 2:46 ` Joshua Yeong
2025-07-03 6:41 ` Wolfram Sang [this message]
2025-07-03 6:41 ` Wolfram Sang
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=aGYmL9CpZHUtEm85@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=Frank.li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=joshua.yeong@starfivetech.com \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-renesas-soc@vger.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.