linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] u300, ux500 and Nomadik changes for v2.6.39
Date: Sun, 13 Mar 2011 21:48:35 +0000	[thread overview]
Message-ID: <20110313214835.GA24370@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <AANLkTikgMq4QbRGZ_3kkzeNBp9aD4YKa-0CRCfs1K57u@mail.gmail.com>

On Fri, Mar 11, 2011 at 09:18:43PM +0100, Linus Walleij wrote:
> Hi Russell,
> 
> if your harddrive is feeling better could you please pull:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-stericsson.git
> for-rmk
> 
> Based on commit dd9c1549edef02290edced639f67b54a25abbe0e:
> Linux 2.6.38-rc7 (2011-03-01 13:55:12 -0800)
> 
> For this set of patches that in short contain:
> - Numerous Nomadik GPIO pin updates for advaced stuff like
>   power management
> - Platform configuration of MUSB for ux500
> - Many platform data updates and refactorings, completing
>   the work to have a single kernel booting across all the
>   ux500 board variants.
> 
> All have been reviewed on the list before.
> Three of these patches may be duplicates of patches

I'm not merging trees which duplicate the patches in my tree.

> already merged in your tree:
>       ARM: 6644/1: mach-ux500: update the U8500 defconfig
>       ARM: perf_event: allow platform-specific interrupt handler
>       mach-ux500: DB8500 PMU support

This is annoying.  These are spread across three entirely different
branches:
"ARM: 6644/1" is part of the defcfg branch.
"ARM: perf_event" is part of someone elses tree merged into devel-stable.
"mach-ux500:" is "ARM: 6776/1:" and is part of the ux500 branch.

I'm intending sending some of these branches as entirely separate pulls
to Linus - particularly the defconfig and devel-stable branches (so that
Linus can see what code outside arch/arm is being modified by other
people and target his complaints about that more appropriately).

Merging your tree is going to destroy my ability to keep this stuff
strictly separate.

I don't mind merging the ux500 branch into devel-stable provided you're
not going to send any further ux500 patches?

  reply	other threads:[~2011-03-13 21:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-11 20:18 [GIT PULL] u300, ux500 and Nomadik changes for v2.6.39 Linus Walleij
2011-03-13 21:48 ` Russell King - ARM Linux [this message]
2011-03-14 11:22   ` Russell King - ARM Linux
2011-03-14 11:46   ` Linus Walleij
2011-03-14 11:51     ` Russell King - ARM Linux
2011-03-14 12:43       ` Linus Walleij
2011-03-14 14:20         ` Linus Walleij

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=20110313214835.GA24370@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;
as well as URLs for NNTP newsgroup(s).