linux-kernel - Re: [PATCH] regmap: introduce regmap_name to fix syscon regmap trace events

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

Message-ID: <20150319152359.6fa4cc35@gandalf.local.home>
Date:	Thu, 19 Mar 2015 15:23:59 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Mark Brown <broonie@...nel.org>
Cc:	Philipp Zabel <p.zabel@...gutronix.de>, kernel@...gutronix.de,
	Pankaj Dubey <pankaj.dubey@...sung.com>,
	Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regmap: introduce regmap_name to fix syscon regmap
 trace events

On Mon, 9 Mar 2015 10:42:40 +0000
Mark Brown <broonie@...nel.org> wrote:

> On Mon, Mar 09, 2015 at 10:48:22AM +0100, Philipp Zabel wrote:
> 
> > Good point. As I see it I have three possiblities now:
> 
> > a) Just #include "../../../drivers/base/regmap/internal.h" in
> >    include/trace/events/regmap.h
> 
> I think this is my preference - it looks ugly which means that it's not
> likely to get abused by anything trying to peer inside the internals
> without setting off alarm bells.

Grumble, reading my inbox backwards seems to make me reply to things
that has already been discussed :-p

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