linux-kernel - Re: [PATCH v2] 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]

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

On Thu, 19 Mar 2015 19:26:12 +0000
Mark Brown <broonie@...nel.org> wrote:

> On Thu, Mar 19, 2015 at 03:22:27PM -0400, Steven Rostedt wrote:
> > Mark Brown <broonie@...nel.org> wrote:
> 
> > > > The regmap trace events expect it to point to a valid struct device and feed
> > > > it to dev_name():
> 
> > > Applied, thanks.
> 
> > Would you mind me sending you a patch that moves the trace file?
> 
> No, please go ahead!

OK.

I pulled your regmap tree:

 git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git

And looked at each of the branches, and I don't see this applied. Is
there another tree I should look at?

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