From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Claudiu <claudiu.beznea@tuxon.dev>
Cc: mturquette@baylibre.com, sboyd@kernel.org,
linux-renesas-soc@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org,
Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>,
Hien Huynh <hien.huynh.px@renesas.com>
Subject: Re: [PATCH 1/2] clk: renesas: r9a08g04{3,4}: Use SEL_SDHI1_STS status configuration for SD1 mux
Date: Mon, 12 Feb 2024 15:01:05 +0100 [thread overview]
Message-ID: <CAMuHMdVmS5cPuWuFaRsA+6TEmJc6B8iZZLFkJpRABQvYgC5p6A@mail.gmail.com> (raw)
In-Reply-To: <20240131102930.1841901-2-claudiu.beznea.uj@bp.renesas.com>
On Thu, Feb 1, 2024 at 9:46 AM Claudiu <claudiu.beznea@tuxon.dev> wrote:
> From: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
>
> The status configuration for SD1 mux clock is SEL_SDHI1_STS. Fix it.
>
> Fixes: 16b86e5c03c5 ("clk: renesas: rzg2l: Refactor SD mux driver")
> Reported-by: Hien Huynh <hien.huynh.px@renesas.com>
> Signed-off-by: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
i.e. will queue in renesas-clk for v6.9, with s/r9a08/r9a07/.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2024-02-12 14:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 10:29 [PATCH 0/2] clk: renesas: r9a08g04{3,4}: Fix typos Claudiu
2024-01-31 10:29 ` [PATCH 1/2] clk: renesas: r9a08g04{3,4}: Use SEL_SDHI1_STS status configuration for SD1 mux Claudiu
2024-02-12 14:01 ` Geert Uytterhoeven [this message]
2024-01-31 10:29 ` [PATCH 2/2] clk: renesas: r9a07g04{3,4}: Fix typo for sel_shdi variable Claudiu
2024-02-12 14:01 ` Geert Uytterhoeven
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=CAMuHMdVmS5cPuWuFaRsA+6TEmJc6B8iZZLFkJpRABQvYgC5p6A@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=hien.huynh.px@renesas.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@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.