public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [QUESTION] mmc: mmci: Howto merge patches
Date: Mon, 17 Dec 2012 15:46:02 +0000	[thread overview]
Message-ID: <20121217154602.GT14363@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAPDyKFpXyVCzFWkyL3+92Zb9hoyKaEV4hpaUYO9O5o71nNmk8w@mail.gmail.com>

On Mon, Dec 17, 2012 at 04:29:51PM +0100, Ulf Hansson wrote:
> Hi Russell and Chris,
> 
> I would like to propose a change of how we handle mmci patches to be
> merged. Instead of going through Russell's arm tree, I would like
> Chris to handle the merge through his mmc tree.
> 
> The reason is simply that patches can have dependencies to the
> protocol layer and in seems a bit unnecessary to wait for another
> merge window to occur to handle these patches.

You're going to have to wait another merge window _anyway_ because no
kernel developer should be stuffing their tree full of patches during
any merge window that have not already been in linux-next well _before_
the merge window.

So like it or not, this merge window already closed to new submissions
maybe two weeks ago.

> Moreover, if most of the mmci patches goes through Chris mmc tree, I
> believe we would minimize the number of possible conflicts. Russell
> will then only need to NACK patches to prevent them from being merged.
> 
> Do you think this could be and acceptable setup for both of you?

The reason that you want to do this is because you're realising that it's
taking a long time for you to get your patches into mainline.  The reason
that I'm being slow with your patches is that you haven't built up the
trust on my side that I can simply say "yes that's fine, I trust your
patches."

That alone is good enough reason for me to say no way to this.

  reply	other threads:[~2012-12-17 15:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-17 15:29 [QUESTION] mmc: mmci: Howto merge patches Ulf Hansson
2012-12-17 15:46 ` Russell King - ARM Linux [this message]
2012-12-17 16:09   ` 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=20121217154602.GT14363@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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