linux-kernel - What's the correct tree to route kprobes patches through?

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: <1421086886.18443.23.camel@linaro.org>
Date:	Mon, 12 Jan 2015 18:21:26 +0000
From:	"Jon Medhurst (Tixy)" <tixy@...aro.org>
To:	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
	"David S. Miller" <davem@...emloft.net>,
	Anil S Keshavamurthy <anil.s.keshavamurthy@...el.com>,
	Ananth N Mavinakayanahalli <ananth@...ibm.com>
Cc:	linux-kernel@...r.kernel.org, Wang Nan <wangnan0@...wei.com>
Subject: What's the correct tree to route kprobes patches through?

Hi All

I'm wondering what the correct route is for getting kprobes patches into
mainline Linux. In particular I'm interested in a patch from Masami
Hiramatsu [1] which is a dependency for some ARM kprobes work we want to
merge. If acceptable, we could submit that one though the ARM
maintainer's tree with our other work.

[1] http://marc.info/?l=linux-kernel&m=142045769001242&w=2
    (kprobes: Pass the original kprobe for preparing optimized kprobe)

Thanks

-- 
Tixy

--
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/