From: Stephen Boyd <sboyd@kernel.org>
To: Zong Li <zong.li@sifive.com>,
devicetree@vger.kernel.org, lee.jones@linaro.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, mturquette@baylibre.com,
palmer@dabbelt.com, paul.walmsley@sifive.com, robh+dt@kernel.org
Cc: Zong Li <zong.li@sifive.com>, Palmer Dabbelt <palmer@rivosinc.com>
Subject: Re: [PATCH v2 4/5] clk: sifive: Add SoCs prefix in each SoCs-dependent data
Date: Tue, 15 Mar 2022 17:02:31 -0700 [thread overview]
Message-ID: <20220316000233.ACFF6C340E8@smtp.kernel.org> (raw)
In-Reply-To: <7728ef662c59449ce954b1b62c6ad5241e07adfb.1646388139.git.zong.li@sifive.com>
Quoting Zong Li (2022-03-04 02:03:20)
> This patch is prerequisite for moving SoCs C files into SoCs header
> files. Currently, fu540-prci.c and fu740-prci.c use same names for
> several macro definitions and variables, it would cause redefinition
> error when we trying to include all stuff in sifive-prci.c. In this
> patch, we also remove the temporary macro definitions which are
> added by previous patch.
>
> Signed-off-by: Zong Li <zong.li@sifive.com>
> Acked-by: Palmer Dabbelt <palmer@rivosinc.com>
> ---
Applied to clk-next
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@kernel.org>
To: Zong Li <zong.li@sifive.com>,
devicetree@vger.kernel.org, lee.jones@linaro.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, mturquette@baylibre.com,
palmer@dabbelt.com, paul.walmsley@sifive.com, robh+dt@kernel.org
Cc: Zong Li <zong.li@sifive.com>, Palmer Dabbelt <palmer@rivosinc.com>
Subject: Re: [PATCH v2 4/5] clk: sifive: Add SoCs prefix in each SoCs-dependent data
Date: Tue, 15 Mar 2022 17:02:31 -0700 [thread overview]
Message-ID: <20220316000233.ACFF6C340E8@smtp.kernel.org> (raw)
In-Reply-To: <7728ef662c59449ce954b1b62c6ad5241e07adfb.1646388139.git.zong.li@sifive.com>
Quoting Zong Li (2022-03-04 02:03:20)
> This patch is prerequisite for moving SoCs C files into SoCs header
> files. Currently, fu540-prci.c and fu740-prci.c use same names for
> several macro definitions and variables, it would cause redefinition
> error when we trying to include all stuff in sifive-prci.c. In this
> patch, we also remove the temporary macro definitions which are
> added by previous patch.
>
> Signed-off-by: Zong Li <zong.li@sifive.com>
> Acked-by: Palmer Dabbelt <palmer@rivosinc.com>
> ---
Applied to clk-next
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2022-03-16 0:02 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 10:03 [PATCH v2 0/5] Refactor the PRCI driver to reduce the complexity Zong Li
2022-03-04 10:03 ` Zong Li
2022-03-04 10:03 ` [PATCH v2 1/5] clk: sifive: duplicate the macro definitions for the time being Zong Li
2022-03-04 10:03 ` Zong Li
2022-03-15 23:59 ` Stephen Boyd
2022-03-15 23:59 ` Stephen Boyd
2022-03-04 10:03 ` [PATCH v2 2/5] dt-bindings: change the macro name of prci in header files and example Zong Li
2022-03-04 10:03 ` Zong Li
2022-03-15 23:59 ` Stephen Boyd
2022-03-15 23:59 ` Stephen Boyd
2022-03-04 10:03 ` [PATCH v2 3/5] riscv: dts: Change the macro name of prci in each device node Zong Li
2022-03-04 10:03 ` Zong Li
2022-03-15 22:54 ` Stephen Boyd
2022-03-15 22:54 ` Stephen Boyd
2022-03-15 22:56 ` Stephen Boyd
2022-03-15 22:56 ` Stephen Boyd
2022-03-16 1:53 ` Zong Li
2022-03-16 1:53 ` Zong Li
2022-03-16 0:02 ` Stephen Boyd
2022-03-16 0:02 ` Stephen Boyd
2022-03-04 10:03 ` [PATCH v2 4/5] clk: sifive: Add SoCs prefix in each SoCs-dependent data Zong Li
2022-03-04 10:03 ` Zong Li
2022-03-16 0:02 ` Stephen Boyd [this message]
2022-03-16 0:02 ` Stephen Boyd
2022-03-04 10:03 ` [PATCH v2 5/5] clk: sifive: Move all stuff into SoCs header files from C files Zong Li
2022-03-04 10:03 ` Zong Li
2022-03-16 0:02 ` Stephen Boyd
2022-03-16 0:02 ` Stephen Boyd
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=20220316000233.ACFF6C340E8@smtp.kernel.org \
--to=sboyd@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=zong.li@sifive.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.