From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mike Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Sowjanya Komatineni <skomatineni@nvidia.com>,
Thierry Reding <treding@nvidia.com>
Subject: linux-next: manual merge of the clk tree with the tegra tree
Date: Fri, 15 Nov 2019 09:26:06 +1100 [thread overview]
Message-ID: <20191115092606.79a65342@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1490 bytes --]
Hi all,
Today's linux-next merge of the clk tree got conflicts in:
include/linux/clk-provider.h
drivers/clk/tegra/clk-super.c
drivers/clk/tegra/clk-sdmmc-mux.c
drivers/clk/tegra/clk-periph.c
drivers/clk/clk.c
between commits:
929490c73870 ("clk: tegra: periph: Add restore_context support")
02ee6fe5e67a ("clk: tegra: clk-super: Fix to enable PLLP branches to CPU")
175ea1f93c33 ("clk: tegra: clk-super: Add restore-context support")
837d3fa941cd ("clk: Add API to get index of the clock parent")
from the tegra tree and commits:
68a14a5634da ("clk: tegra: clk-super: Fix to enable PLLP branches to CPU")
f8fd97521d63 ("clk: tegra: clk-super: Add restore-context support")
2b8cfd6b52cb ("clk: tegra: periph: Add restore_context support")
d9b86cc48283 ("clk: Add API to get index of the clock parent")
from the clk tree.
These are different version of the same patches (presumably).
I fixed it up (I just used the versions from the clk tree (since even
though the commits have the smae author dates, the clk tree versions were
committed later) 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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-11-14 22:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 22:26 Stephen Rothwell [this message]
2019-11-15 9:43 ` linux-next: manual merge of the clk tree with the tegra tree Thierry Reding
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=20191115092606.79a65342@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=skomatineni@nvidia.com \
--cc=treding@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox