From: Stephen Boyd <sboyd@kernel.org>
To: Marek Vasut <marek.vasut+renesas@mailbox.org>, linux-clk@vger.kernel.org
Cc: Marek Vasut <marek.vasut+renesas@mailbox.org>,
Alex Helms <alexander.helms.jy@renesas.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Luca Ceresoli <luca.ceresoli@bootlin.com>,
Magnus Damm <magnus.damm@gmail.com>,
Michael Turquette <mturquette@baylibre.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Tom Rix <trix@redhat.com>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 1/3] clk: vc5: Fix .driver_data content in i2c_device_id
Date: Wed, 10 May 2023 14:27:13 -0700 [thread overview]
Message-ID: <817a2a01770e9a90317ad3f81219ca43.sboyd@kernel.org> (raw)
In-Reply-To: <20230507133906.15061-1-marek.vasut+renesas@mailbox.org>
Quoting Marek Vasut (2023-05-07 06:39:04)
> The .driver_data content in i2c_device_id table must match the
> .data content in of_device_id table, else device_get_match_data()
> would return bogus value on i2c_device_id match. Align the two
> tables.
>
> The i2c_device_id table is now converted from of_device_id using
> 's@.compatible = "idt,\([^"]\+"\), .data = \(.*\)@"\1, .driver_data = (kernel_ulong_t)\2@'
>
> Fixes: 9adddb01ce5f ("clk: vc5: Add structure to describe particular chip features")
> Signed-off-by: Marek Vasut <marek.vasut+renesas@mailbox.org>
> ---
Applied to clk-next
prev parent reply other threads:[~2023-05-10 21:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-07 13:39 [PATCH 1/3] clk: vc5: Fix .driver_data content in i2c_device_id Marek Vasut
2023-05-07 13:39 ` [PATCH 2/3] clk: vc7: " Marek Vasut
2023-05-08 13:05 ` Geert Uytterhoeven
2023-05-10 21:27 ` Stephen Boyd
2023-05-07 13:39 ` [PATCH 3/3] clk: rs9: " Marek Vasut
2023-05-08 13:05 ` Geert Uytterhoeven
2023-05-10 21:27 ` Stephen Boyd
2023-05-08 12:39 ` [PATCH 1/3] clk: vc5: " Luca Ceresoli
2023-05-08 13:01 ` Geert Uytterhoeven
2023-05-10 21:27 ` 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=817a2a01770e9a90317ad3f81219ca43.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=alexander.helms.jy@renesas.com \
--cc=geert+renesas@glider.be \
--cc=linux-clk@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=magnus.damm@gmail.com \
--cc=marek.vasut+renesas@mailbox.org \
--cc=mturquette@baylibre.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=trix@redhat.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 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.