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, torvalds@linux-foundation.org,
linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: [GIT PULL v4.6] MDB Linux Kernel Debugger x86/x86_64
Date: Tue, 15 Mar 2016 11:24:58 +1100 [thread overview]
Message-ID: <20160315112458.7248d665@canb.auug.org.au> (raw)
In-Reply-To: <1457999823.11972.143.camel@perches.com>
Hi Joe,
On Mon, 14 Mar 2016 16:57:03 -0700 Joe Perches <joe@perches.com> wrote:
>
> On Mon, 2016-03-14 at 17:50 -0600, Jeffrey Merkey wrote:
> > The following changes since commit b562e44f507e863c6792946e4e1b1449fbbac85d:
> >
> > Linux 4.5 (2016-03-13 21:28:54 -0700)
> >
> > are available in the git repository at:
> >
> > https://github.com/jeffmerkey/linux.git tags/mdb-v4.5-signed
> >
> > for you to fetch changes up to 2e9c184e1215dca2b4c59c347f40a0986b8e7460:
> >
> > Add MDB Debugger to linux v4.5 (2016-03-14 15:17:44 -0600)
>
> If Linus doesn't pull this, Stephen, could you please add this
> tree to -next so it has some testing and validation done?
Well, I really need a request from the ongoing maintainer and also some
indication of which kernel release (if any) it is likely to be merged
into ...
As a general rule, I do not add trees to linux-next during the merge
window (there have been some special cases when something was going in
during that merge window).
I do note that the single commit in that tag has no Signed-off-by,
Reviewed-by or Acked-by tags at all. As such I can't see Linus merging
it as is. The commit message also has no detail at all. It is also
based on v4.5 which was only released yesterday.
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2016-03-15 0:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160314235035.GA5799@localhost.localdomain>
2016-03-14 23:57 ` [GIT PULL v4.6] MDB Linux Kernel Debugger x86/x86_64 Joe Perches
2016-03-15 0:24 ` Stephen Rothwell [this message]
2016-03-15 0:40 ` Jeffrey Merkey
2016-03-15 2:03 ` Stephen Rothwell
2016-03-15 15:16 ` Theodore Ts'o
2016-03-16 23:27 ` Jeffrey Merkey
2016-03-18 5:31 ` Jeffrey Merkey
2016-03-18 5:40 ` Joe Perches
2016-03-18 5:43 ` Jeffrey Merkey
2016-03-25 8:36 ` Ingo Molnar
2016-03-25 17:17 ` Jeffrey Merkey
2016-03-25 17:27 ` Jeffrey Merkey
2016-03-25 23:01 ` Jeffrey Merkey
2016-03-25 23:02 ` Jeffrey Merkey
2016-03-26 1:48 ` Stephen Rothwell
2016-03-26 1:56 ` Jeffrey Merkey
2016-03-26 1:48 ` Stephen Rothwell
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=20160315112458.7248d665@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jeffmerkey@gmail.com \
--cc=joe@perches.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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