mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
	kernel@pengutronix.de, Pankaj Dubey <pankaj.dubey@samsung.com>,
	Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regmap: introduce regmap_name to fix syscon regmap trace events
Date: Thu, 19 Mar 2015 19:59:11 +0000	[thread overview]
Message-ID: <20150319195911.GB2869@sirena.org.uk> (raw)
In-Reply-To: <20150319155228.12b834e9@gandalf.local.home>

[-- Attachment #1: Type: text/plain, Size: 569 bytes --]

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.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

      reply	other threads:[~2015-03-19 19:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-06 14:16 Philipp Zabel
2015-03-07 10:57 ` Mark Brown
2015-03-09  9:48   ` Philipp Zabel
2015-03-09 10:42     ` Mark Brown
2015-03-19 19:23       ` Steven Rostedt
2015-03-19 19:52     ` Steven Rostedt
2015-03-19 19:59       ` Mark Brown [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150319195911.GB2869@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=p.zabel@pengutronix.de \
    --cc=pankaj.dubey@samsung.com \
    --cc=rostedt@goodmis.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®