linux-kernel - kgdb-next not pushed to Linus for 3.19

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <54AC2F5D.9050405@linaro.org>
Date:	Tue, 06 Jan 2015 18:54:21 +0000
From:	Daniel Thompson <daniel.thompson@...aro.org>
To:	Jason Wessel <jason.wessel@...driver.com>
CC:	lkml <linux-kernel@...r.kernel.org>,
	"kgdb-bugreport@...ts.sourceforge.net" 
	<kgdb-bugreport@...ts.sourceforge.net>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...hat.com>,
	John Stultz <john.stultz@...aro.org>,
	Sumit Semwal <sumit.semwal@...aro.org>,
	Joe Perches <joe@...ches.com>,
	Steven Rostedt <rostedt@...dmis.org>
Subject: kgdb-next not pushed to Linus for 3.19

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.

Daniel.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/