From: Lee Jones <lee@kernel.org>
To: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: core: Un-constify mfd_cell.of_reg
Date: Fri, 18 Aug 2023 16:58:15 +0100 [thread overview]
Message-ID: <20230818155815.GY986605@google.com> (raw)
In-Reply-To: <aa8de668f39f76c98e443c7cce2834e813807111.1692188782.git.mirq-linux@rere.qmqm.pl>
On Wed, 16 Aug 2023, Michał Mirosław wrote:
> of_reg is the only constant member of struct mfd_cell. It seems to be
Sorry, what?
struct mfd_cell {
const char *name;
[...]
const struct mfd_cell_acpi_match *acpi_match;
[...]
const struct software_node *swnode;
[...]
const char *of_compatible;
[...]
const u64 of_reg;
[...]
const struct resource *resources;
[...]
const char * const *parent_supplies;
[...]
};
> accidental and prevents dynamically filling in mfd_cells that use of_reg.
> Remove the `const`.
Dynamically filling mfd_cells is generally frowned upon.
Please submit this with the code that will be using it.
> Fixes: 466a62d7642f ("mfd: core: Make a best effort attempt to match devices with the correct of_nodes")
> Signed-off-by: Michał Mirosław <mirq-linux@rere.qmqm.pl>
> ---
> include/linux/mfd/core.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/mfd/core.h b/include/linux/mfd/core.h
> index 47e7a3a61ce6..e8bcad641d8c 100644
> --- a/include/linux/mfd/core.h
> +++ b/include/linux/mfd/core.h
> @@ -92,7 +92,7 @@ struct mfd_cell {
> * (above) when matching OF nodes with devices that have identical
> * compatible strings
> */
> - const u64 of_reg;
> + u64 of_reg;
>
> /* Set to 'true' to use 'of_reg' (above) - allows for of_reg=0 */
> bool use_of_reg;
> --
> 2.39.2
>
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2023-08-18 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 12:27 [PATCH] mfd: core: Un-constify mfd_cell.of_reg Michał Mirosław
2023-08-18 15:58 ` Lee Jones [this message]
2023-08-19 0:11 ` Michał Mirosław
2023-08-21 8:13 ` Lee Jones
2023-08-22 19:36 ` Michał Mirosław
2023-08-24 12:19 ` Lee Jones
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=20230818155815.GY986605@google.com \
--to=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
/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.