All of lore.kernel.org
 help / color / mirror / Atom feed
From: pawel.moll@arm.com (Pawel Moll)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] vexpress: soc changes for v3.8
Date: Fri, 26 Oct 2012 18:45:32 +0100	[thread overview]
Message-ID: <1351273532.9454.43.camel@hornet> (raw)
In-Reply-To: <201210261718.08983.arnd@arndb.de>

On Fri, 2012-10-26 at 18:18 +0100, Arnd Bergmann wrote:
> Are you sure it's the same commit that Mike has in his tree?
> Is this not the tree that is part of linux-next?

Damn, I am seriously confused now... I'm looking at next-20121026 in
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git and
I'm _not_ seeing the vexpress clk drivers! Neither I can find the
patches in git://git.linaro.org/people/mturquette/linux.git clk-next.

Am I doing something wrong or just looking not where I should? You seem
to be able to see some -next vexpress clk patches - where about?

Mike, you said:

On Thu, 2012-10-11 at 23:40 +0100, Mike Turquette wrote:
> I've taken these into my new clk-next towards 3.8.  That branch is not
> yet pushed out publicly but will be after -rc1 is released.
 
Has this happened yet?

Pawe?

  reply	other threads:[~2012-10-26 17:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-18 17:05 [GIT PULL] vexpress: soc changes for v3.8 Pawel Moll
2012-10-26 13:37 ` Arnd Bergmann
2012-10-26 14:02   ` Pawel Moll
2012-10-26 16:44 ` Arnd Bergmann
2012-10-26 16:54   ` Pawel Moll
2012-10-26 17:00     ` Arnd Bergmann
2012-10-26 17:10       ` Pawel Moll
2012-10-26 17:18         ` Arnd Bergmann
2012-10-26 17:45           ` Pawel Moll [this message]
2012-10-26 19:26             ` Arnd Bergmann

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=1351273532.9454.43.camel@hornet \
    --to=pawel.moll@arm.com \
    --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.