All of lore.kernel.org
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] [for 3.5] request pull of dt on arch-mmp
Date: Wed, 9 May 2012 01:56:51 -0700	[thread overview]
Message-ID: <CAOesGMhD480FNUa+QFC_dmxu7aP4jMt5MhfX2MzpT24=1-bqhg@mail.gmail.com> (raw)
In-Reply-To: <CAN1soZyvYVnN61HakQFKav-B1msY8UuVqDJso4OEe2zSaD=ruA@mail.gmail.com>

Hi,

On Sun, May 6, 2012 at 8:50 PM, Haojian Zhuang <haojian.zhuang@gmail.com> wrote:
> On Sat, May 5, 2012 at 4:44 PM, Haojian Zhuang <haojian.zhuang@gmail.com> wrote:
>> Hi Arnd & Olof,
>>
>> Please help to pull dt branch on arch-mmp git tree.
>>
>> The following changes since commit 69964ea4c7b68c9399f7977aa5b9aa6539a6a98a:
>>
>> ?Linux 3.4-rc5 (2012-04-29 15:19:10 -0700)
>>
> Hi Arnd & Olof,
>
> Pleae help to pull dt branch on arch-pxa git tree.
>
> Since some power patches are depend on irq driver code and it's
> changed in dt branch.
> I merged these power patches in dt branch to avoid building issue.

The way to do this is to still send two branches, one that includes
the dt code, and one that contains the power management changes but
that is based on the dt branch, and then explicitly mention in the
pull request that there is dependencies between the two.

Can you please do that, i.e. reset the dt branch back to only contain
the dt changes, and then take what is essentially this later pull and
do that as a 'pm' branch instead?


Thanks,

-Olof

  reply	other threads:[~2012-05-09  8:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-05  8:44 [GIT PULL] [for 3.5] request pull of dt on arch-mmp Haojian Zhuang
2012-05-07  3:50 ` Haojian Zhuang
2012-05-09  8:56   ` Olof Johansson [this message]
2012-05-14  1:46     ` Haojian Zhuang

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='CAOesGMhD480FNUa+QFC_dmxu7aP4jMt5MhfX2MzpT24=1-bqhg@mail.gmail.com' \
    --to=olof@lixom.net \
    --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 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.