Linux clock framework development
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@mailbox.org>
To: Biju Das <biju.das.jz@bp.renesas.com>,
	Alex Helms <alexander.helms.jy@renesas.com>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>
Cc: linux-clk@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
	linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 2/2] clk: vc7: Use i2c_get_match_data() instead of device_get_match_data()
Date: Sun, 16 Jul 2023 17:57:35 +0200	[thread overview]
Message-ID: <a89c516d-8d25-98ec-c93d-cc7250244569@mailbox.org> (raw)
In-Reply-To: <20230716154442.93908-3-biju.das.jz@bp.renesas.com>

On 7/16/23 17:44, Biju Das wrote:
> The device_get_match_data(), is to get match data for firmware interfaces
> such as just OF/ACPI. This driver has I2C matching table as well. Use
> i2c_get_match_data() to get match data for I2C, ACPI and DT-based
> matching.
> 
> Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>

Reviewed-by: Marek Vasut <marek.vasut+renesas@mailbox.org>

  reply	other threads:[~2023-07-16 15:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-16 15:44 [PATCH 0/2] Use i2c_get_match_data() Biju Das
2023-07-16 15:44 ` [PATCH 1/2] clk: vc5: Use i2c_get_match_data() instead of device_get_match_data() Biju Das
2023-07-16 15:56   ` Marek Vasut
2023-07-17  7:35   ` Geert Uytterhoeven
2023-07-17  7:46     ` Biju Das
2023-07-17 12:56       ` Luca Ceresoli
2023-07-20 19:10         ` Biju Das
2023-07-16 15:44 ` [PATCH 2/2] clk: vc7: " Biju Das
2023-07-16 15:57   ` Marek Vasut [this message]
2023-07-17  7:36   ` Geert Uytterhoeven
2023-07-17  7:48     ` Biju Das

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=a89c516d-8d25-98ec-c93d-cc7250244569@mailbox.org \
    --to=marek.vasut@mailbox.org \
    --cc=alexander.helms.jy@renesas.com \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=geert+renesas@glider.be \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox