From: "Heiko Stübner" <heiko@sntech.de>
To: Chukun Pan <amadeus@jmu.edu.cn>, FUKAUMI Naoki <naoki@radxa.com>
Cc: chris.obbard@collabora.com, conor+dt@kernel.org,
devicetree@vger.kernel.org, krzk+dt@kernel.org,
linux-rockchip@lists.infradead.org, robh@kernel.org,
sebastian.reichel@collabora.com
Subject: Re: [PATCH 3/3] arm64: dts: rockchip: change spi-max-frequency for Radxa ROCK 3C
Date: Mon, 24 Jun 2024 16:58:21 +0200 [thread overview]
Message-ID: <2557120.Y4W8hZkJsM@diego> (raw)
In-Reply-To: <DBE7B5A56069764A+b5680896-bc71-4af8-9d56-bd6828595e74@radxa.com>
Am Sonntag, 23. Juni 2024, 06:24:56 CEST schrieb FUKAUMI Naoki:
> Hi,
>
> Thank you very much for your comment!
>
> On 6/23/24 13:04, Chukun Pan wrote:
> > Hi,
> >> SPI NOR flash chip may vary, so use safe(lowest) spi-max-frequency.
> >
> > I don't think a fixes tag is needed, because there is no documentation
> > for this. See also (sfc part):
> > https://lore.kernel.org/lkml/d7de2213-8dd2-42ec-9a30-a569ac71be3e@kwiboo.se/
>
> I see, I'll remove fixes tag in v2.
> btw, is this change reasonable(acceptable)?
it is, also no need to resend, I just dropped the Fixes tag myself
next prev parent reply other threads:[~2024-06-24 14:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-23 2:33 [PATCH 1/3] arm64: dts: rockchip: add SFC support for Radxa ROCK 5B FUKAUMI Naoki
2024-06-23 2:33 ` [PATCH 2/3] arm64: dts: rockchip: add (but disabled) SFC node for Radxa ROCK 5A FUKAUMI Naoki
2024-06-23 2:33 ` [PATCH 3/3] arm64: dts: rockchip: change spi-max-frequency for Radxa ROCK 3C FUKAUMI Naoki
2024-06-23 4:04 ` Chukun Pan
2024-06-23 4:24 ` FUKAUMI Naoki
2024-06-24 10:00 ` Chukun Pan
2024-06-24 21:29 ` FUKAUMI Naoki
2024-06-24 14:58 ` Heiko Stübner [this message]
2024-06-24 16:20 ` [PATCH 1/3] arm64: dts: rockchip: add SFC support for Radxa ROCK 5B Heiko Stuebner
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=2557120.Y4W8hZkJsM@diego \
--to=heiko@sntech.de \
--cc=amadeus@jmu.edu.cn \
--cc=chris.obbard@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=naoki@radxa.com \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.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;
as well as URLs for NNTP newsgroup(s).