All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leo Liang <ycliang@andestech.com>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: Lukasz Majewski <lukma@denx.de>,
	Sean Anderson <seanga2@gmail.com>, <u-boot@lists.denx.de>
Subject: Re: [PATCH 1/1] clk: sifive: avoid declaring static variables in includes
Date: Mon, 9 Sep 2024 13:47:00 +0800	[thread overview]
Message-ID: <Zt6L1Ikm8e42M7IY@swlinux02> (raw)
In-Reply-To: <20240216231804.141470-1-heinrich.schuchardt@canonical.com>

On Sat, Feb 17, 2024 at 12:18:04AM +0100, Heinrich Schuchardt wrote:
> The existing code is unnecessarily convoluted:
> 
> Arrays __prci_init_clocks_fu[5|7]40  are initialized with data.
> In separate includes fu[5|7]40-prci.h the size of the arrays is provided as
> constants.
> 
> By moving the structures prci_clk_fu[5|7]40 to the respective code modules
> we can directly use ARRAY_SIZE() to access the size of the data used for
> initialization.
> 
> Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
> ---
>  drivers/clk/sifive/fu540-prci.c  |  7 ++++++-
>  drivers/clk/sifive/fu540-prci.h  | 22 ----------------------
>  drivers/clk/sifive/fu740-prci.c  |  7 ++++++-
>  drivers/clk/sifive/fu740-prci.h  | 22 ----------------------
>  drivers/clk/sifive/sifive-prci.c |  3 +--
>  drivers/clk/sifive/sifive-prci.h |  4 ++++
>  6 files changed, 17 insertions(+), 48 deletions(-)
>  delete mode 100644 drivers/clk/sifive/fu540-prci.h
>  delete mode 100644 drivers/clk/sifive/fu740-prci.h

Reviewed-by: Leo Yu-Chi Liang <ycliang@andestech.com>

      parent reply	other threads:[~2024-09-09  5:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-16 23:18 [PATCH 1/1] clk: sifive: avoid declaring static variables in includes Heinrich Schuchardt
2024-04-11  3:16 ` Sean Anderson
2024-09-09  5:47 ` Leo Liang [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=Zt6L1Ikm8e42M7IY@swlinux02 \
    --to=ycliang@andestech.com \
    --cc=heinrich.schuchardt@canonical.com \
    --cc=lukma@denx.de \
    --cc=seanga2@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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.