The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Liam Girdwood <lrg@slimlogic.co.uk>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] voltage regulator updates for 2.6.31-rc1
Date: Mon, 15 Jun 2009 10:28:31 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.2.01.0906151027210.3305@localhost.localdomain> (raw)
In-Reply-To: <20090615171720.GH6106@sirena.org.uk>



On Mon, 15 Jun 2009, Mark Brown wrote:

> On Mon, Jun 15, 2009 at 09:29:54AM -0700, Linus Torvalds wrote:
> > On Mon, 15 Jun 2009, Liam Girdwood wrote:
> 
> > >  include/linux/regulator/lp3971.h             |   51 +++
> 
> > Why the heck would "lp3971.h" be under "include/linux"? That makes no 
> > sense what-so-ever. 
> 
> > Why isn't it just
> 
> > 	drivers/regulator/lp3971.c
> > 	drivers/regulator/lp3971.h
> 
> It defines a platform data structure for the architecture code which
> instantiates the driver to use to pass configuration to the driver.  If
> the header were in drivers/regulator then any system using one of these
> regulators would need to peer into drivers/regulator in order to set up
> the driver.

A quick grep shows:

	[torvalds@nehalem linux]$ git grep lp3971.h
	drivers/regulator/lp3971.c:#include <linux/regulator/lp3971.h>

ie _nobody_ includes lp3971.h except for lp3971.c.

So tell me again, why is that lp3971.h file separate from the only driver 
that uses it?

		Linus

  reply	other threads:[~2009-06-15 17:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-15 11:24 [GIT PULL] voltage regulator updates for 2.6.31-rc1 Liam Girdwood
2009-06-15 16:29 ` Linus Torvalds
2009-06-15 17:17   ` Mark Brown
2009-06-15 17:28     ` Linus Torvalds [this message]
2009-06-15 18:04       ` Mark Brown

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=alpine.LFD.2.01.0906151027210.3305@localhost.localdomain \
    --to=torvalds@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@slimlogic.co.uk \
    /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