linux-kernel - linux-next: Add secondary kgdb tree

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: <20181217164253.5ficzs4zr4dxbemu@holly.lan>
Date:   Mon, 17 Dec 2018 16:42:53 +0000
From:   Daniel Thompson <daniel.thompson@...aro.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Jason Wessel <jason.wessel@...driver.com>,
        kgdb-bugreport@...ts.sourceforge.net
Subject: linux-next: Add secondary kgdb tree

Hi Stephen

Is there any change you could add my kgdb tree to the roster for
linux-next :

https://git.kernel.org/pub/scm/linux/kernel/git/danielt/linux.git kgdb/for-next

I'm currently collecting kgdb patches for v4.21 together and at the
moment it looks like the PR for kgdb will come from my tree this dev
cycle.

This will leave you with two kgdb trees in this list which I assume
isn't great for you (although Jason's tree isn't really changing much
at the moment so I guess merging it is a nop). Anyhow I've made a diary
note to follow this up in two kernel cycles time and decide which one
we want to keep on the roster. Is that OK for you?

Daniel.