linux-kernel - Re: New MFD tree for linux-next

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20130318111357.0eb626f200ce7dfa68d6e81c@canb.auug.org.au>
Date:	Mon, 18 Mar 2013 11:13:57 +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 Mon, 18 Mar 2013 01:11:02 +0100 Samuel Ortiz <sameo@...ux.intel.com> wrote:
>
> On Mon, Mar 18, 2013 at 10:45:20AM +1100, Stephen Rothwell wrote:
> > On Mon, 18 Mar 2013 00:39:07 +0100 Samuel Ortiz <sameo@...ux.intel.com> wrote:
> > >
> > > > I assume that you are still using the for-next branch?
> > > I will update for-next branch to be in sync with mfd-next until the 3.10 merge
> > > window closes. After that I'll probably delete the mfd-2.6.git tree.
> > 
> > I meant "I assume that I should still fetch the for-next branch
> > of ...sameo/mfd-next.git".  If that has changed, please let me know.
> Sorry for the misunderstanding, I was not clear enough: mfd-next master is
> replacing mfd-2.6 for-next and mfd-fixes master is replacing mfd-2.6 for-linus.
> So no need to pull mfd-next for-next.
> 
> I deleted all branches but master from both mfd-next and mfd-fixes, so things
> should be clearer now.

OK, I will fix this up for tomorrow.

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

Content of type "application/pgp-signature" skipped