From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Abel Vesa <abel.vesa@nxp.com>,
Mike Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: Abel Vesa <abel.vesa@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Marek Vasut <marex@denx.de>, Qin Jian <qinjian@cqplus1.com>
Subject: linux-next: manual merge of the clk-imx tree with the clk tree
Date: Mon, 3 Apr 2023 09:28:24 +1000 [thread overview]
Message-ID: <20230403092824.67117617@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1537 bytes --]
Hi all,
Today's linux-next merge of the clk-imx tree got a conflict in:
include/linux/clk-provider.h
between commit:
d54c1fd4a51e ("clk: Add Sunplus SP7021 clock driver")
from the clk tree and commit:
27fc5ec673b5 ("clk: Introduce devm_clk_hw_register_gate_parent_data()")
from the clk-imx tree.
These add the same macro, but the letter has the docmenting comment wrong.
I fixed it up (I just used the former) and can carry the fix as
necessary. This is now fixed as far as linux-next is concerned, but any
non trivial conflicts should be mentioned to your upstream maintainer
when your tree is submitted for merging. You may also want to consider
cooperating with the maintainer of the conflicting tree to minimise any
particularly complex conflicts.
--
Cheers,
Stephen Rothwell
diff --cc include/linux/clk-provider.h
index faad3cdc1e48,92b7c794c627..000000000000
--- a/include/linux/clk-provider.h
+++ b/include/linux/clk-provider.h
@@@ -608,9 -608,9 +608,10 @@@ struct clk *clk_register_gate(struct de
__devm_clk_hw_register_gate((dev), NULL, (name), (parent_name), NULL, \
NULL, (flags), (reg), (bit_idx), \
(clk_gate_flags), (lock))
+
/**
- * devm_clk_hw_register_gate - register a gate clock with the clock framework
+ * devm_clk_hw_register_gate_parent_data - register a gate clock with the
+ * clock framework
* @dev: device that is registering this clock
* @name: name of this clock
* @parent_data: parent clk data
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2023-04-02 23:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230403092824.67117617@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=abel.vesa@linaro.org \
--cc=abel.vesa@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=marex@denx.de \
--cc=mturquette@baylibre.com \
--cc=qinjian@cqplus1.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
all inboxes | Powered by JetHome®