From: Joe Perches <joe@perches.com>
To: Daniel Thompson <daniel.thompson@linaro.org>
Cc: Jason Wessel <jason.wessel@windriver.com>,
lkml <linux-kernel@vger.kernel.org>,
"kgdb-bugreport@lists.sourceforge.net"
<kgdb-bugreport@lists.sourceforge.net>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@redhat.com>,
John Stultz <john.stultz@linaro.org>,
Sumit Semwal <sumit.semwal@linaro.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: kgdb-next not pushed to Linus for 3.19
Date: Tue, 06 Jan 2015 10:57:42 -0800 [thread overview]
Message-ID: <1420570662.2652.36.camel@perches.com> (raw)
In-Reply-To: <54AC2F5D.9050405@linaro.org>
On Tue, 2015-01-06 at 18:54 +0000, Daniel Thompson wrote:
> Hi Jason
>
> I'm trying to figure out what to do with my long-outstanding kgdb/kdb
> patches in preparation for the 3.20 merge window.
>
> As of now I have five pending patch sets some of which are well over six
> months old (and none have nay outstanding review comments).
>
> When I raised this with you a couple of months ago, two of the patch
> sets did land in your kgdb-next tree. However nothing seems to have
> happened since then and I couldn't find any messages from you during the
> 3.19 merge window.
>
> I'm afraid I don't know what else I need to do to progress things.
>
> I do plan to do routine rebasing and resending of my patchsets but,
> based on the past experience, that seems unlikely to be enough to get
> the code delivered in 3.20.
>
> Do you think I would be better sending these patches via someone else?
> In any case, advice would be very welcome.
Andrew?
I think Daniel's kgdb patches are bug fixes.
Can you please pick them up?
next prev parent reply other threads:[~2015-01-06 18:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 18:54 kgdb-next not pushed to Linus for 3.19 Daniel Thompson
2015-01-06 18:57 ` Joe Perches [this message]
2015-01-06 21:21 ` Andrew Morton
2015-01-06 22:30 ` Jason Wessel
2015-01-07 13:53 ` Daniel Thompson
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=1420570662.2652.36.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=daniel.thompson@linaro.org \
--cc=jason.wessel@windriver.com \
--cc=john.stultz@linaro.org \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=sumit.semwal@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.