From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: "Chen-Yu Tsai" <wens@csie.org>,
"Emilio López" <emilio@elopez.com.ar>,
"Stephen Boyd" <sboyd@kernel.org>,
"Michael Turquette" <mturquette@baylibre.com>,
"Samuel Holland" <samuel@sholland.org>
Cc: Samuel Holland <samuel@sholland.org>,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-sunxi@lists.linux.dev
Subject: Re: Re: [PATCH 1/2] clk: sunxi: Limit legacy clocks to 32-bit ARM
Date: Mon, 04 Jul 2022 22:05:57 +0200 [thread overview]
Message-ID: <4196041.ejJDZkT8p0@kista> (raw)
In-Reply-To: <8956393.CDJkKcVGEf@jernej-laptop>
Dne sobota, 02. julij 2022 ob 21:09:18 CEST je Jernej Škrabec napisal(a):
> Dne sobota, 02. julij 2022 ob 21:01:34 CEST je Samuel Holland napisal(a):
> > The sunxi legacy clocks were never compatible with any 64-bit SoC,
> > so there is no point in building them as part of a 64-bit ARM kernel.
> > They make even less sense being built in to a 64-bit RISC-V kernel.
> >
> > Signed-off-by: Samuel Holland <samuel@sholland.org>
>
> Reviewed-by: Jernej Skrabec <jernej.skrabec@gmail.com>
Applied both, thanks!
Best regards,
Jernej
WARNING: multiple messages have this Message-ID (diff)
From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: "Chen-Yu Tsai" <wens@csie.org>,
"Emilio López" <emilio@elopez.com.ar>,
"Stephen Boyd" <sboyd@kernel.org>,
"Michael Turquette" <mturquette@baylibre.com>,
"Samuel Holland" <samuel@sholland.org>
Cc: Samuel Holland <samuel@sholland.org>,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-sunxi@lists.linux.dev
Subject: Re: Re: [PATCH 1/2] clk: sunxi: Limit legacy clocks to 32-bit ARM
Date: Mon, 04 Jul 2022 22:05:57 +0200 [thread overview]
Message-ID: <4196041.ejJDZkT8p0@kista> (raw)
In-Reply-To: <8956393.CDJkKcVGEf@jernej-laptop>
Dne sobota, 02. julij 2022 ob 21:09:18 CEST je Jernej Škrabec napisal(a):
> Dne sobota, 02. julij 2022 ob 21:01:34 CEST je Samuel Holland napisal(a):
> > The sunxi legacy clocks were never compatible with any 64-bit SoC,
> > so there is no point in building them as part of a 64-bit ARM kernel.
> > They make even less sense being built in to a 64-bit RISC-V kernel.
> >
> > Signed-off-by: Samuel Holland <samuel@sholland.org>
>
> Reviewed-by: Jernej Skrabec <jernej.skrabec@gmail.com>
Applied both, thanks!
Best regards,
Jernej
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-07-04 20:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-02 19:01 [PATCH 1/2] clk: sunxi: Limit legacy clocks to 32-bit ARM Samuel Holland
2022-07-02 19:01 ` Samuel Holland
2022-07-02 19:01 ` [PATCH 2/2] clk: sunxi: Do not select the PRCM MFD Samuel Holland
2022-07-02 19:01 ` Samuel Holland
2022-07-02 19:10 ` Jernej Škrabec
2022-07-02 19:10 ` Jernej Škrabec
2022-07-02 19:09 ` [PATCH 1/2] clk: sunxi: Limit legacy clocks to 32-bit ARM Jernej Škrabec
2022-07-02 19:09 ` Jernej Škrabec
2022-07-04 20:05 ` Jernej Škrabec [this message]
2022-07-04 20:05 ` Jernej Škrabec
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=4196041.ejJDZkT8p0@kista \
--to=jernej.skrabec@gmail.com \
--cc=emilio@elopez.com.ar \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=mturquette@baylibre.com \
--cc=samuel@sholland.org \
--cc=sboyd@kernel.org \
--cc=wens@csie.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.