From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Jean Delvare <khali@linux-fr.org>
Cc: Julia Lawall <julia@diku.dk>,
i2c@lm-sensors.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 1/4] drivers/i2c: Drop redundant includes of moduleparam.h
Date: Thu, 15 Nov 2007 07:42:28 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.0.9999.0711150739490.9736@localhost.localdomain> (raw)
In-Reply-To: <20071115131915.0eb34c98@hyperion.delvare>
On Thu, 15 Nov 2007, Jean Delvare wrote:
... snip ...
> I share Robert's point of view here. Relying on header files
> including each other is usually not a good idea, as build then
> breaks when the headers are cleaned up or reorganized.
... more snip ...
> If there's a fundamental reason why module.h has to include
> moduleparam.h, then both headers should be merged in a single file.
> If not, then both header files should be clearly split and drivers
> should include each of them as needed. Either way, header files must
> be fixed first, and drivers adjusted in consequence. So, I'm not
> taking this patch, sorry.
keeping this short and sweet, i updated my wiki page on this topic:
http://www.crashcourse.ca/wiki/index.php/Module.h_and_moduleparam.h
i think the fundamental question here is whether this is even
cleanable without massive disruption.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://crashcourse.ca
========================================================================
prev parent reply other threads:[~2007-11-15 12:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 21:32 Julia Lawall
2007-11-13 21:34 ` Robert P. J. Day
2007-11-14 6:09 ` Julia Lawall
2007-11-14 9:21 ` Robert P. J. Day
2007-11-15 12:19 ` Jean Delvare
2007-11-15 12:42 ` Robert P. J. Day [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=alpine.LFD.0.9999.0711150739490.9736@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=i2c@lm-sensors.org \
--cc=julia@diku.dk \
--cc=kernel-janitors@vger.kernel.org \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.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®