From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
linux-kernel@vger.kernel.org
Subject: Re: mmotm 2008-09-13-03-09 uploaded
Date: Thu, 18 Sep 2008 21:32:38 +0100 [thread overview]
Message-ID: <1221769958.6892.80.camel@odin> (raw)
In-Reply-To: <20080919035248.d3187001.sfr@canb.auug.org.au>
On Fri, 2008-09-19 at 03:52 +1000, Stephen Rothwell wrote:
> Hi Andrew, Liam,
>
> On Thu, 18 Sep 2008 02:23:53 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
> >
> > > Can I just confirm the repository & branch you are pulling as I've
> > > recently left Wolfson and now work for myself (I will no longer have
> > > guaranteed access to the Wolfson git repositories). I've also moved
> > > regulator development over to kernel.org:-
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/lrg/voltage-2.6.git #dev
> > >
> >
> > Please send that off to Stephen for linux-next inclusion.
>
> I have this:
>
> Liam Girdwood <lg@opensource.wolfsonmicro.com>
> voltage git://git.kernel.org/pub/scm/linux/kernel/git/lrg/voltage-2.6.git#reg-for-linus
>
> in the linux-next list already. Do I assume that some changes are needed
> (email and branch)?
>
Yes, email and branch have changed.
For next it should be :-
Liam Girdwood <lrg@slimlogic.co.uk>
voltage git://git.kernel.org/pub/scm/linux/kernel/git/lrg/voltage-2.6.git#for-linus
Thanks
Liam
prev parent reply other threads:[~2008-09-18 20:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-13 10:11 mmotm 2008-09-13-03-09 uploaded akpm
2008-09-18 6:01 ` KAMEZAWA Hiroyuki
2008-09-18 6:26 ` Andrew Morton
2008-09-18 8:51 ` Liam Girdwood
2008-09-18 9:23 ` Andrew Morton
2008-09-18 9:37 ` Liam Girdwood
2008-09-18 17:52 ` Stephen Rothwell
2008-09-18 20:32 ` Liam Girdwood [this message]
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=1221769958.6892.80.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.