From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: Takahiro.Kuwano@infineon.com, miquel.raynal@bootlin.com,
trini@konsulko.com
Cc: mwalle@kernel.org, conor@kernel.org, u-boot@lists.denx.de,
Hiroyuki.Saito2@infineon.com, venkatesh.abbarapu@amd.com,
p-mantena@ti.com, vaishnav.a@ti.com, prasad.kummari@amd.com,
pratyush@kernel.org, vigneshr@ti.com,
marek.vasut+renesas@mailbox.org
Subject: Re: [RFH] SPI and SPI-NOR patch help
Date: Tue, 24 Feb 2026 12:23:33 +0200 [thread overview]
Message-ID: <4e4d660e-b9a1-48ce-aa60-ae63bea6bbde@linaro.org> (raw)
In-Reply-To: <90d5d396d2ec4888a4359ca4b2392b8d@infineon.com>
On 2/24/26 10:39 AM, Takahiro.Kuwano@infineon.com wrote:
>> Takahiro recently accepted becoming a designated reviewer for SPI NOR
>> in Linux, and I think his expertise would be highly valuable in U-Boot
>> as well. Takahiro, if you have the bandwidth, would you be open to
>> becoming a designated reviewer here too? Or maybe see how things are
>> going in Linux first? No pressure.
>>
> Yes, I'm open to do that.
>
Wonderful!
> To sync with Linux, we need to isolate stacked/parallel support from core first.
> https://patchwork.ozlabs.org/project/uboot/cover/20251119-amd-cleanup-v1-0-c555bd85e6e4@infineon.com/
+1
next prev parent reply other threads:[~2026-02-24 13:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 16:46 [RFH] SPI and SPI-NOR patch help Tom Rini
2026-02-14 18:58 ` Conor Dooley
2026-02-16 8:21 ` Michael Walle
2026-02-16 15:31 ` Tom Rini
2026-02-18 9:23 ` Miquel Raynal
2026-02-18 14:20 ` Peter Robinson
2026-02-19 10:26 ` Miquel Raynal
2026-02-19 12:13 ` Tudor Ambarus
2026-02-19 20:57 ` Tom Rini
2026-02-20 7:35 ` Tudor Ambarus
2026-02-20 15:07 ` Tom Rini
2026-02-24 8:39 ` Takahiro.Kuwano
2026-02-24 10:23 ` Tudor Ambarus [this message]
2026-02-24 15:40 ` Tom Rini
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=4e4d660e-b9a1-48ce-aa60-ae63bea6bbde@linaro.org \
--to=tudor.ambarus@linaro.org \
--cc=Hiroyuki.Saito2@infineon.com \
--cc=Takahiro.Kuwano@infineon.com \
--cc=conor@kernel.org \
--cc=marek.vasut+renesas@mailbox.org \
--cc=miquel.raynal@bootlin.com \
--cc=mwalle@kernel.org \
--cc=p-mantena@ti.com \
--cc=prasad.kummari@amd.com \
--cc=pratyush@kernel.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vaishnav.a@ti.com \
--cc=venkatesh.abbarapu@amd.com \
--cc=vigneshr@ti.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