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
Subject: Re: [GIT PULL] MDB Linux Kernel Debugger v4.8 (for kbuild robot testing)
Date: Mon, 03 Oct 2016 19:42:50 -0700 [thread overview]
Message-ID: <1475548970.1923.5.camel@perches.com> (raw)
In-Reply-To: <20161004132927.3ff5d0ce@canb.auug.org.au>
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.
next prev parent reply other threads:[~2016-10-04 2:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 0:17 [GIT PULL] MDB Linux Kernel Debugger v4.8 (for kbuild robot testing) Jeffrey Merkey
2016-10-04 1:47 ` Joe Perches
2016-10-04 2:29 ` Stephen Rothwell
2016-10-04 2:42 ` Joe Perches [this message]
2016-10-04 2:54 ` Jeffrey Merkey
2016-10-04 3:14 ` Jeffrey Merkey
-- strict thread matches above, loose matches on Subject: below --
2016-10-04 0:09 Jeffrey Merkey
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=1475548970.1923.5.camel@perches.com \
--to=joe@perches.com \
--cc=jeffmerkey@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox