From: Randy Dunlap <randy.dunlap@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jiri Kosina <jkosina@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: [GIT PATCH] HID and USB HID update for 2.6.21-rc2
Date: Wed, 28 Feb 2007 10:33:09 -0800 [thread overview]
Message-ID: <20070228103309.84a3a9e4.randy.dunlap@oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0702281022380.12485@woody.linux-foundation.org>
On Wed, 28 Feb 2007 10:28:10 -0800 (PST) Linus Torvalds wrote:
>
>
> On Wed, 28 Feb 2007, Linus Torvalds wrote:
> >
> > In other words, there is *zero* excuse for that braindamage.
>
> To be clear:
>
> - in header files, we put "common definitions":
>
> * #defines
> * data structure declarations
> * external function and data declarations
> * inline functions ("nicer but otherwise equivalent to a #define")
>
> - but we do *not* put
>
> * actual real code
> * actual real data
>
> because those go into C files.
>
> Yes, yes, all rules have exceptions, and sometimes we have ugly header
> files. For an example of a pre-existing ugly header file that breaks these
> rules, just look at <asm-i386/bugs.h> for example. Yeah, it only gets
> included from one place, but it *still* shouldn't have code in it. It grew
> over time, and none of the individual events were ever really big enough
> for anybody to say "ok, we should clean this up and create a bugs.c file
> in arch/i386/kernel".
It's on my TODO list... just not high priority.
> I'm sure there are other examples of the exceptions too. But I do not want
> to add *new* ugly stuff, and I certainly refuse to do it after we're
> already long past a merge window.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2007-02-28 18:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-28 10:19 Jiri Kosina
2007-02-28 17:09 ` Linus Torvalds
2007-02-28 17:25 ` Jiri Kosina
2007-02-28 17:34 ` Linus Torvalds
2007-02-28 17:41 ` Jiri Kosina
2007-02-28 18:20 ` Linus Torvalds
2007-02-28 18:28 ` Linus Torvalds
2007-02-28 18:33 ` Randy Dunlap [this message]
2007-02-28 18:29 ` Jiri Kosina
2007-02-28 18:39 ` Linus Torvalds
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=20070228103309.84a3a9e4.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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®