All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Krzysztof Kozlowski <krzk@kernel.org>
Subject: linux-next: manual merge of the pinctrl tree with the arm-soc tree
Date: Tue, 31 Jan 2017 16:29:51 +1100	[thread overview]
Message-ID: <20170131162951.3de4bcd6@canb.auug.org.au> (raw)

Hi Linus,

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

  arch/arm/mach-exynos/suspend.c

between commit:

  b4765037fc8c ("ARM: EXYNOS: Constify list of retention registers")

from the arm-soc tree and commit:

  07731019c59c ("pinctrl: samsung: Move retention control from mach-exynos to the pinctrl driver")

from the pinctrl tree.

I fixed it up (the latter removed the code updated by the former, so I
just did that) 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

             reply	other threads:[~2017-01-31  5:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-31  5:29 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-06  1:13 linux-next: manual merge of the pinctrl tree with the arm-soc tree Stephen Rothwell
2022-12-06  1:13 ` Stephen Rothwell
2022-12-06 15:04 ` Andy Shevchenko
2022-12-06 15:04   ` Andy Shevchenko
2022-11-18  5:06 Stephen Rothwell
2022-11-18  5:06 ` Stephen Rothwell
2021-12-17  6:29 Stephen Rothwell
2021-12-17  6:29 ` Stephen Rothwell
2021-12-17  8:02 ` Arnd Bergmann
2021-12-17  8:02   ` Arnd Bergmann
2021-12-17 11:02 ` Andy Shevchenko
2021-12-17 11:02   ` Andy Shevchenko
2014-11-10  6:34 Stephen Rothwell

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=20170131162951.3de4bcd6@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=krzk@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=m.szyprowski@samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.