From: Linus Walleij <linus.walleij@linaro.org>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] Renesas ARM-based SoC: KZM-A9-GT for 3.7 #2
Date: Thu, 06 Sep 2012 07:35:21 +0000 [thread overview]
Message-ID: <CACRpkdaj0Jc3TKgkC6AUt-j4t+hQg5weGrceTfROHaYmW1KsBw@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdZBOjO124w3WwPpL7ekf2dU1w2HCub9EG=LUxFSPn8Ayw@mail.gmail.com>
On Thu, Sep 6, 2012 at 7:58 AM, Linus Walleij <linus.walleij@linaro.org> wrote:
> On Thu, Sep 6, 2012 at 12:44 AM, Olof Johansson <olof@lixom.net> wrote:
>
>> So, we can't pull in this branch with its dependency without an agreement that
>> Linus holds a branch stable with at least the pcf857x patch on it. Linus?
>
> OMG! OK let's claim that it's stable now then, it's close enough
> to the merge window.
Oh! And by the way, make sure you pull in the "devel" branch:
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git devel
My "for-next" is a mixdown of fixes and devel, so the stuff that
will really go into next merge window is on devel.
Yours,
Linus Walleij
WARNING: multiple messages have this Message-ID (diff)
From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Renesas ARM-based SoC: KZM-A9-GT for 3.7 #2
Date: Thu, 6 Sep 2012 09:35:21 +0200 [thread overview]
Message-ID: <CACRpkdaj0Jc3TKgkC6AUt-j4t+hQg5weGrceTfROHaYmW1KsBw@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdZBOjO124w3WwPpL7ekf2dU1w2HCub9EG=LUxFSPn8Ayw@mail.gmail.com>
On Thu, Sep 6, 2012 at 7:58 AM, Linus Walleij <linus.walleij@linaro.org> wrote:
> On Thu, Sep 6, 2012 at 12:44 AM, Olof Johansson <olof@lixom.net> wrote:
>
>> So, we can't pull in this branch with its dependency without an agreement that
>> Linus holds a branch stable with at least the pcf857x patch on it. Linus?
>
> OMG! OK let's claim that it's stable now then, it's close enough
> to the merge window.
Oh! And by the way, make sure you pull in the "devel" branch:
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git devel
My "for-next" is a mixdown of fixes and devel, so the stuff that
will really go into next merge window is on devel.
Yours,
Linus Walleij
next prev parent reply other threads:[~2012-09-06 7:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 5:47 [GIT PULL] Renesas ARM-based SoC: KZM-A9-GT for 3.7 #2 Simon Horman
2012-08-30 5:47 ` Simon Horman
2012-08-30 5:47 ` [PATCH] ARM: shmobile: kzm9g: use gpio-keys instead of gpio-keys-polled Simon Horman
2012-08-30 5:47 ` Simon Horman
2012-09-05 22:44 ` [GIT PULL] Renesas ARM-based SoC: KZM-A9-GT for 3.7 #2 Olof Johansson
2012-09-05 22:44 ` Olof Johansson
2012-09-06 5:58 ` Linus Walleij
2012-09-06 5:58 ` Linus Walleij
2012-09-06 6:18 ` Simon Horman
2012-09-06 6:18 ` Simon Horman
2012-09-06 7:16 ` Linus Walleij
2012-09-06 7:16 ` Linus Walleij
2012-09-06 7:35 ` Linus Walleij [this message]
2012-09-06 7:35 ` 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=CACRpkdaj0Jc3TKgkC6AUt-j4t+hQg5weGrceTfROHaYmW1KsBw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--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.