From: Simon Horman <horms@verge.net.au>
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 06:18:07 +0000 [thread overview]
Message-ID: <20120906061807.GA3326@verge.net.au> (raw)
In-Reply-To: <CACRpkdZBOjO124w3WwPpL7ekf2dU1w2HCub9EG=LUxFSPn8Ayw@mail.gmail.com>
On Thu, Sep 06, 2012 at 07:58:02AM +0200, Linus Walleij 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.
>
> Ironically his was caused by a Samsung commit (IIRC) which I
> applied to the GPIO tree but shouldn't be there (instead to be
> funneled through ARM SoC) so I had to take it out after
> a week. So maybe we're not so good off with these mixtures
> of "ARM SoC pulls GPIO" vs "ACK and push it all through ARM SoC"
> hm, maybe it's just one of those things we have to live with...
It seems to me that I should rebase the my branch and it can
then go through either the ARM SoC or GPIO tree. Either is fine by me.
As an aside, the patch does include a defconfig change.
Olof, Should that be broken out into a separate patch?
next prev parent reply other threads:[~2012-09-06 6:18 UTC|newest]
Thread overview: 7+ 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 ` [PATCH] ARM: shmobile: kzm9g: use gpio-keys instead of gpio-keys-polled Simon Horman
2012-09-05 22:44 ` [GIT PULL] Renesas ARM-based SoC: KZM-A9-GT for 3.7 #2 Olof Johansson
2012-09-06 5:58 ` Linus Walleij
2012-09-06 6:18 ` Simon Horman [this message]
2012-09-06 7:16 ` Linus Walleij
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=20120906061807.GA3326@verge.net.au \
--to=horms@verge.net.au \
--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).