From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Joe Perches <joe@perches.com>
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: Tue, 4 Oct 2016 13:29:27 +1100 [thread overview]
Message-ID: <20161004132927.3ff5d0ce@canb.auug.org.au> (raw)
In-Reply-To: <1475545624.1923.3.camel@perches.com>
Hi Joe,
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.
Has there been much recent discussion/review/testing of this tree? Is
it likely that Linus will merge it? (Just asking, I haven't been
following it.)
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2016-10-04 2:29 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 [this message]
2016-10-04 2:42 ` Joe Perches
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=20161004132927.3ff5d0ce@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jeffmerkey@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
/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