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

Date:	Thu, 19 Mar 2015 19:59:11 +0000
From:	Mark Brown <broonie@...nel.org>
To:	Steven Rostedt <rostedt@...dmis.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 Thu, Mar 19, 2015 at 03:52:28PM -0400, Steven Rostedt wrote:

> I'm not sure what you mean be driver-level vs subsystem-level. How is
> this a subsystem level as regmap happens to be in the drivers code.

Lots of generic, subsystem level code lives in drivers/ - most
directories in there have a bunch of drivers together with the
subsystem code that supports them.  In the case of regmap the 
percentage of generic code is very high as it's mostly there as
a helper subsystem hiding register map access details from drivers
that sit in other subsystems.

Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)