Message-ID: <1475548970.1923.5.camel@perches.com>
Subject: Re: [GIT PULL] MDB Linux Kernel Debugger v4.8 (for kbuild robot
 testing)
From: Joe Perches <joe@perches.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jeffrey Merkey <jeffmerkey@gmail.com>, linux-kernel@vger.kernel.org
Date: Mon, 03 Oct 2016 19:42:50 -0700
In-Reply-To: <20161004132927.3ff5d0ce@canb.auug.org.au>
References: <20161004001720.GA351@166-70-60-63.utopia.xmission.net>
         <1475545624.1923.3.camel@perches.com>
         <20161004132927.3ff5d0ce@canb.auug.org.au>
Content-Type: text/plain; charset="ISO-8859-1"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1466
Lines: 45


On Tue, 2016-10-04 at 13:29 +1100, Stephen Rothwell wrote:
> Hi Joe,

Hi Stephen.

> On Mon, 03 Oct 2016 18:47:04 -0700 Joe Perches <joe@perches.com> wrote:
> > 
> > On Mon, 2016-10-03 at 18:17 -0600, Jeffrey Merkey wrote:
> > > The following changes since commit c8d2bc9bc39ebea8437fd974fdbc21847bb897a3:
> > > 
> > >   Linux 4.8 (2016-10-02 16:24:33 -0700)
> > > 
> > > are available in the git repository at:
> > > 
> > >   https://github.com/jeffmerkey/linux.git mdb-v4.8
> > > 
> > > for you to fetch changes up to 8e3486647ebcef24e67fc2eebe49f3641a4ffc95:
> > > 
> > >   Add MDB Debugger to Linux Kernel v4.8 (2016-10-02 20:33:55 -0600)  
> > 
> > 
> > Stephen, can this tree be added to -next to get some
> > exposure for the next cycle?
> 
> 
> I don't add trees during the merge window (unless they contain stuff
> for the current merge window and, even then, only rarely).  Also, I
> only take requests from the maintainer/owner of the tree.

No worries, it's really a request for Jeff who doesn't seem
to know the process very well.

Jeff, you really should get this into -next before sending a
pull request to Linus for this large bit of code.

> Has there been much recent discussion/review/testing of this tree?

Not to my knowledge for about 6 months now.

> Is it likely that Linus will merge it?  (Just asking, I haven't been
> following it.)

Dunno.  I'd guess it will _not_ be merged without some time
in -next and a compelling reason to use it.