linux-kernel - Re: [PATCH 0/3] ARM Coresight: Enhance ETM tracing control

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-prev] [day] [month] [year] [list]

Date:	Fri, 6 Dec 2013 00:23:45 +0000
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	Adrien Vergé <adrienverge@...il.com>,
	Christopher Covington <cov@...eaurora.org>,
	Randy Dunlap <rdunlap@...radead.org>,
	Will Deacon <will.deacon@....com>,
	linux-kernel@...r.kernel.org,
	Ben Dooks <ben.dooks@...ethink.co.uk>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Dietmar Eggemann <dietmar.eggemann@....com>,
	linux-arm-kernel@...ts.infradead.org,
	"zhangwei(Jovi)" <jovi.zhangwei@...wei.com>
Subject: Re: [PATCH 0/3] ARM Coresight: Enhance ETM tracing control

On Thu, Dec 05, 2013 at 04:06:10PM -0800, Greg Kroah-Hartman wrote:
> On Thu, Dec 05, 2013 at 06:54:49PM -0500, Adrien Vergé wrote:
> > > Well, these patches were incorrect, so that's not really a valid
> > > question :)
> > 
> > Should I correct the pid size and send them again?
> 
> I'm not the ARM maintainer, so I can't say if I would reject them or
> not.

Neither am I someone who knows this code; it was contributed by TI, and
I assume TI had I use for it.  I've no idea what that was or how it's
even used - it's not something I particularly care about.

I'd much rather someone else who has a use for ETM (and thus knows what
it should/can do) look after it.
--
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/