public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Olof Johansson <olof@lixom•net>, Arnd Bergmann <arnd@arndb•de>,
	linux-arm-kernel@lists•infradead.org
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	Simon Horman <horms+renesas@verge•net.au>
Subject: linux-next: manual merge of the arm-soc tree with Linus' tree
Date: Thu, 21 Jan 2016 09:40:22 +1100	[thread overview]
Message-ID: <20160121094022.33e25d08@canb.auug.org.au> (raw)

Hi all,

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

  MAINTAINERS

between commit:

  4a121096db9c ("MAINTAINERS: Update mailing list for Renesas SoC Development")

from Linus' tree and commit:

  804b0d7011ee ("MAINTAINERS: Remove link to oss.renesas.com which is closed")

from the arm-soc tree.

I fixed it up (see below) and can carry the fix as necessary (no action
is required).

-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au

diff --cc MAINTAINERS
index 5461ecc147dc,0939ce1bdb71..000000000000
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@@ -1531,9 -1526,8 +1541,8 @@@ F:	drivers/media/platform/s5p-jpeg
  ARM/SHMOBILE ARM ARCHITECTURE
  M:	Simon Horman <horms@verge•net.au>
  M:	Magnus Damm <magnus.damm@gmail•com>
 -L:	linux-sh@vger•kernel.org
 -Q:	http://patchwork.kernel.org/project/linux-sh/list/
 +L:	linux-renesas-soc@vger•kernel.org
- W:	http://oss.renesas.com
 +Q:	http://patchwork.kernel.org/project/linux-renesas-soc/list/
  T:	git git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git next
  S:	Supported
  F:	arch/arm/boot/dts/emev2*

             reply	other threads:[~2016-01-20 22:40 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-20 22:40 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-05-27  0:39 linux-next: manual merge of the arm-soc tree with Linus' tree Stephen Rothwell
2022-05-27 15:38 ` Hawkins, Nick
2022-05-28  0:29   ` Stephen Rothwell
2019-06-23 22:54 Stephen Rothwell
2018-10-28 23:14 Stephen Rothwell
2018-10-29 15:02 ` Tony Lindgren
2018-10-28 23:08 Stephen Rothwell
2016-09-05  0:58 Stephen Rothwell
2016-09-05 18:26 ` Russell King - ARM Linux
2016-09-06 10:17   ` Arnd Bergmann
2016-09-06 10:42     ` Russell King - ARM Linux
2016-09-25 16:07   ` Robert Jarzmik
2015-08-23 23:55 Stephen Rothwell
2015-06-01  0:25 Stephen Rothwell
2015-06-01  7:12 ` Michal Simek
2014-01-30  0:19 Stephen Rothwell
2014-01-30  5:33 ` Kevin Hilman
2014-01-30 21:47   ` Mike Turquette
2014-01-23  0:23 Stephen Rothwell
2013-08-27  8:29 Stephen Rothwell
2013-08-27 16:17 ` Stephen Warren
2013-08-28  0:06   ` Stephen Rothwell
2013-08-27  8:26 Stephen Rothwell
2013-07-08  4:03 Stephen Rothwell
2013-03-18  3:49 Stephen Rothwell
2012-10-04  4:33 Stephen Rothwell
2012-07-30  2:53 Stephen Rothwell
2012-03-15  6:50 Stephen Rothwell
2012-03-15  9:51 ` Laurent Pinchart
2012-03-15 20:01   ` Arnd Bergmann
2012-03-15 21:36     ` Rafael J. Wysocki
2012-03-08  6:07 Stephen Rothwell
2011-11-24  0:58 Stephen Rothwell
2011-11-24 15:55 ` Arnd Bergmann
2011-11-06 23:33 Stephen Rothwell
2011-11-07 19:07 ` Arnd Bergmann

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=20160121094022.33e25d08@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=arnd@arndb$(echo .)de \
    --cc=horms+renesas@verge$(echo .)net.au \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=olof@lixom$(echo .)net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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