linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Drew Fustini <dfustini@tenstorrent.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Mike Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>, Olof Johansson <olof@lixom.net>,
	Arnd Bergmann <arnd@arndb.de>,
	ARM <linux-arm-kernel@lists.infradead.org>,
	Drew Fustini <drew@pdp7.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Yangtao Li <frank.li@vivo.com>
Subject: Re: linux-next: manual merge of the clk tree with the arm-soc tree
Date: Fri, 12 Jul 2024 00:00:12 -0700	[thread overview]
Message-ID: <ZpDUfIspyPL2wbLA@x1> (raw)
In-Reply-To: <20240712095825.6e1224d9@canb.auug.org.au>

On Fri, Jul 12, 2024 at 09:58:25AM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> Today's linux-next merge of the clk tree got a conflict in:
> 
>   MAINTAINERS
> 
> between commit:
> 
>   480d9a6083f4 ("MAINTAINERS: thead: add git tree")
> 
> from the arm-soc tree and commit:
> 
>   1037885b309c ("dt-bindings: clock: Document T-Head TH1520 AP_SUBSYS controller")
> 
> 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 MAINTAINERS
> index 44cff47c2594,04eb5587ffa7..000000000000
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@@ -19382,8 -19322,9 +19382,10 @@@ M:	Guo Ren <guoren@kernel.org
>   M:	Fu Wei <wefu@redhat.com>
>   L:	linux-riscv@lists.infradead.org
>   S:	Maintained
>  +T:	git https://github.com/pdp7/linux.git
> + F:	Documentation/devicetree/bindings/clock/thead,th1520-clk-ap.yaml
>   F:	arch/riscv/boot/dts/thead/
> + F:	include/dt-bindings/clock/thead,th1520-clk-ap.h
>   
>   RNBD BLOCK DRIVERS
>   M:	Md. Haris Iqbal <haris.iqbal@ionos.com>

Thank you for fixing this up. The resolution looks good to me.

Drew


  reply	other threads:[~2024-07-12  7:00 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-11 23:58 linux-next: manual merge of the clk tree with the arm-soc tree Stephen Rothwell
2024-07-12  7:00 ` Drew Fustini [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-11-22  8:41 Stephen Rothwell
2016-11-22  9:36 ` Geert Uytterhoeven
2016-11-22 23:59   ` Stephen Rothwell
2016-03-01  3:57 Stephen Rothwell
2016-03-01  4:00 ` Stephen Rothwell
2016-03-01  8:38   ` Nicolas Ferre
2015-02-03  5:31 Stephen Rothwell
2015-02-03 18:25 ` Mike Turquette
2015-02-03  5:28 Stephen Rothwell
2014-01-13  5:06 Stephen Rothwell
2014-01-26 20:59 ` Tomasz Figa
2014-01-26 21:05   ` Tomasz Figa
2013-06-17  7:27 Stephen Rothwell
2013-06-17 18:49 ` Mike Turquette
2013-04-19  7:27 Stephen Rothwell
2013-04-19  9:47 ` Pawel Moll
2013-02-02 12:27 Stephen Rothwell
2013-02-04 17:54 ` Mike Turquette
2012-11-28  6:12 Stephen Rothwell
2012-10-30  4:06 Stephen Rothwell
2012-10-30 10:11 ` Mike Turquette
2012-10-30 10:39   ` Pawel Moll
2012-09-10  6:14 Stephen Rothwell
2012-09-10 15:24 ` Linus Walleij
2012-09-10 16:51   ` Mike Turquette
2012-07-13  5:14 Stephen Rothwell
2012-07-13 15:10 ` Rob Herring
2012-07-13 17:27   ` Mike Turquette

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=ZpDUfIspyPL2wbLA@x1 \
    --to=dfustini@tenstorrent.com \
    --cc=arnd@arndb.de \
    --cc=drew@pdp7.com \
    --cc=frank.li@vivo.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=olof@lixom.net \
    --cc=sboyd@kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).