[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20130316132753.591db4c078d06db297ba46a8@canb.auug.org.au>
Date: Sat, 16 Mar 2013 13:27:53 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Samuel Ortiz <sameo@...ux.intel.com>
Cc: linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: New MFD tree for linux-next
Hi Samuel,
On Fri, 15 Mar 2013 17:46:25 +0100 Samuel Ortiz <sameo@...ux.intel.com> wrote:
>
> On Thu, Mar 14, 2013 at 01:02:01AM +0100, Samuel Ortiz wrote:
> >
> > I am moving the MFD development from mfd-2.6.git/for-next to a new mfd-next
> > tree:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/sameo/mfd-next.git
> >
> > Could you please point linux-next at it ? Many thanks in advance.
Done. I assume that you are still using the for-next branch?
> I'm also carrying MFD fixes through the mfd-fixes tree:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/sameo/mfd-fixes.git
>
> Could you please also add it to linux-next ?
What branch should I use of that?
BTW, those two trees look very similar (in fact "diff -u <(git ls-remote
mfd) <(git ls-remote mfd-fixes)" only shows a couple of differences in
all the refs). You do realise that I can use 2 different branches of one
tree, right (as can others)?
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists