linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: "Stephen Rothwell" <sfr@canb.auug.org.au>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"David Lanzendörfer" <david.lanzendoerfer@o2s.ch>
Subject: Re: linux-next: manual merge of the mmc-uh tree with the sunxi tree
Date: Wed, 21 Jan 2015 13:12:02 +0100	[thread overview]
Message-ID: <20150121121202.GF4367@lukather> (raw)
In-Reply-To: <CAPDyKFq4TyiadznYCM-dGmeu799vWevBt1XVZ4DALhv-3bP=AA@mail.gmail.com>

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

Hi,

On Wed, Jan 21, 2015 at 12:27:09PM +0100, Ulf Hansson wrote:
> On 20 January 2015 at 04:17, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > Hi Ulf,
> >
> > Today's linux-next merge of the mmc-uh tree got a conflict in
> > drivers/mmc/host/sunxi-mmc.c between commit 6c09bb851e57 ("mmc: sunxi:
> > Convert MMC driver to the standard clock phase API") from the sunxi
> > tree and commit 776e24c502da ("mmc: sunxi: Removing unused code") from
> > the mmc-uh tree.
> >
> > I fixed it up (the former includes the latter change) and can carry the
> > fix as necessary (no action is required).
> 
> Maxime,
> 
> I can't find the sunxi tree, is it listed in MAINTAINERS?

No, it's not, I should probably add it :)

It is here: https://git.kernel.org/cgit/linux/kernel/git/mripard/linux.git/

> I know I have acked below patch, but that was quite a I while ago. Is
> there any reason to why I can't take it through my mmc tree at this
> point?
> "mmc: sunxi: Convert MMC driver to the standard clock phase API".

It still is needed to preserve bisectability, which is why you acked
it in the first place. Otherwise, you would end up with a build
breakage in the clock tree, because the mmc driver would still use the
removed custom phase functions, and a failing MMC driver in your tree
because the MMC clocks would not have the phase callbacks implemented.

It's a pretty wide window of failure, and especially for the build
breakage, I don't think it would be wise to split these patches.

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2015-01-21 12:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-20  3:17 linux-next: manual merge of the mmc-uh tree with the sunxi tree Stephen Rothwell
2015-01-21 11:27 ` Ulf Hansson
2015-01-21 12:07   ` Geert Uytterhoeven
2015-01-21 12:12   ` Maxime Ripard [this message]
2015-01-21 13:42     ` Ulf Hansson

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=20150121121202.GF4367@lukather \
    --to=maxime.ripard@free-electrons.com \
    --cc=david.lanzendoerfer@o2s.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=ulf.hansson@linaro.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).