From: Stephen Boyd <sboyd@kernel.org>
To: Hal Feng <hal.feng@starfivetech.com>,
linux-clk@vger.kernel.org, linux-mm@kvack.org,
oe-kbuild-all@lists.linux.dev
Cc: Michael Turquette <mturquette@baylibre.com>,
Conor Dooley <conor.dooley@microchip.com>,
Paul Gazzillo <paul@pgazz.com>,
Necip Fazil Yildiran <fazilyildiran@gmail.com>,
Emil Renner Berthing <emil.renner.berthing@canonical.com>,
Hal Feng <hal.feng@starfivetech.com>,
Xingyu Wu <xingyu.wu@starfivetech.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 2/2] clk: starfive: Delete the redundant dev_set_drvdata() in JH7110 clock drivers
Date: Mon, 17 Apr 2023 18:13:21 -0700 [thread overview]
Message-ID: <cb922046c9e9ae2359b7f22fa7436e2c.sboyd@kernel.org> (raw)
In-Reply-To: <20230417074115.30786-3-hal.feng@starfivetech.com>
Quoting Hal Feng (2023-04-17 00:41:15)
> The dev_set_drvdata() is no longer needed after we used a wrapper
> struct to get the data in auxiliary driver.
>
> Cc: Xingyu Wu <xingyu.wu@starfivetech.com>
> Fixes: d1aae0663023 ("clk: starfive: Avoid casting iomem pointers")
> Signed-off-by: Hal Feng <hal.feng@starfivetech.com>
> ---
Applied to clk-next
prev parent reply other threads:[~2023-04-18 1:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 7:41 [PATCH v1 0/2] A fix for StarFive " Hal Feng
2023-04-17 7:41 ` [PATCH v1 1/2] clk: starfive: Fix RESET_STARFIVE_JH7110 can't be selected in a specified case Hal Feng
2023-04-17 9:54 ` Conor Dooley
2023-04-17 10:06 ` Hal Feng
2023-04-17 10:18 ` Conor Dooley
2023-04-18 0:22 ` Stephen Boyd
2023-04-18 2:14 ` Hal Feng
2023-04-18 6:31 ` Conor Dooley
2023-04-18 12:42 ` Hal Feng
2023-04-17 7:41 ` [PATCH v1 2/2] clk: starfive: Delete the redundant dev_set_drvdata() in JH7110 clock drivers Hal Feng
2023-04-18 1:13 ` Stephen Boyd [this message]
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=cb922046c9e9ae2359b7f22fa7436e2c.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=emil.renner.berthing@canonical.com \
--cc=fazilyildiran@gmail.com \
--cc=hal.feng@starfivetech.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mturquette@baylibre.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paul@pgazz.com \
--cc=xingyu.wu@starfivetech.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