mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Greg KH <gregkh@suse.de>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>, Greg KH <greg@kroah.com>,
	anton@samba.org, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix pciehp driver on non ACPI systems
Date: Thu, 6 Apr 2006 20:14:22 +0200	[thread overview]
Message-ID: <20060406181422.GA6998@mars.ravnborg.org> (raw)
In-Reply-To: <20060406175704.GA30949@suse.de>

On Thu, Apr 06, 2006 at 10:57:04AM -0700, Greg KH wrote:
> > > > >  #include "../pci.h"
> > 
> > When one introdues relative apths like the above this is a good sign
> > that the header file ought to move to a common place somewhere in
> > include/.
> 
> No, this is a pci-core only header file.  I really don't want to have
> these in include/linux/pci.h as no one other than the pci core, or pci
> hotplug drivers need to use it.

But that hold true for other stuff in include/* also.

The guideline is (my understanding):
- Use .h files only when declarations are shared by more than one .c
  file
- Put the .h file in same dir as the .c files, iff the .c files are all
  in same dir (and include using #include "file.h")
- For bigger subsystems create an include/<subsystem> dir for shared .h
  files (and include using #include <file.h>)
- For smaller subsystems create an include/linux/<subsystem> dir for
  shared .h files (and include using #include <file.h>)

And then we also have:
- For Greg's pci-core keep the shared .h file with the .c files
  (and include using #include "../file.h")

See why this sticks out a bit.

Not that I imply the above guidlines are strictly followed - but thats
the best I have seen.

	Sam

  reply	other threads:[~2006-04-06 18:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-06 10:17 Anton Blanchard
2006-04-06 16:05 ` Greg KH
2006-04-06 17:41   ` Randy.Dunlap
2006-04-06 17:46     ` Sam Ravnborg
2006-04-06 17:57       ` Greg KH
2006-04-06 18:14         ` Sam Ravnborg [this message]
2006-04-12 22:28           ` Greg KH
2006-04-06 18:27     ` Greg KH
2006-04-06 18:58       ` Dave Hansen

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=20060406181422.GA6998@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=akpm@osdl.org \
    --cc=anton@samba.org \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /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

Powered by JetHome