linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mike Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	Horatiu Vultur <horatiu.vultur@microchip.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: manual merge of the clk tree with Linus' tree
Date: Wed, 30 Mar 2022 09:07:05 +1100	[thread overview]
Message-ID: <20220330090705.1c9cbd0b@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1230 bytes --]

Hi all,

Today's linux-next merge of the clk tree got a conflict in:

  drivers/clk/Kconfig

between commit:

  aa091a6a91df ("clk: lan966x: Fix linking error")

from Linus' tree and commit:

  7cd5c56054f8 ("clk: COMMON_CLK_LAN966X should depend on SOC_LAN966")

from the clk tree.

I fixed it up (see below) 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 drivers/clk/Kconfig
index d4d67fbae869,d8c5f30487a9..000000000000
--- a/drivers/clk/Kconfig
+++ b/drivers/clk/Kconfig
@@@ -231,8 -241,7 +241,9 @@@ config COMMON_CLK_GEMIN
  
  config COMMON_CLK_LAN966X
  	bool "Generic Clock Controller driver for LAN966X SoC"
+ 	depends on SOC_LAN966 || COMPILE_TEST
 +	depends on HAS_IOMEM
 +	depends on OF
  	help
  	  This driver provides support for Generic Clock Controller(GCK) on
  	  LAN966X SoC. GCK generates and supplies clock to various peripherals

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2022-03-29 22:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29 22:07 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-06-06 23:13 linux-next: manual merge of the clk tree with Linus' tree Stephen Rothwell
2017-07-24  0:37 Stephen Rothwell
2015-02-20  0:17 Stephen Rothwell
2014-01-29  3:25 Stephen Rothwell
2014-01-29  8:53 ` Nicolas Ferre
2013-08-27  9:03 Stephen Rothwell
2013-08-27 10:09 ` James Hogan
2013-08-27 15:44   ` Sören Brinkmann
2013-08-27 16:53     ` Mike Turquette
2013-08-28  0:04       ` Stephen Rothwell
2013-08-28  7:22         ` Stephen Rothwell
2013-08-28  8:05           ` James Hogan
2013-08-28 15:48           ` Sören Brinkmann

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=20220330090705.1c9cbd0b@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=geert+renesas@glider.be \
    --cc=horatiu.vultur@microchip.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mturquette@baylibre.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;
as well as URLs for NNTP newsgroup(s).