From: Matthew Wilcox <matthew@wil.cx>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] another project or two
Date: Mon, 04 Jun 2007 13:48:12 +0000 [thread overview]
Message-ID: <20070604134812.GC23968@parisc-linux.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0706040528251.31127@localhost.localdomain>
On Mon, Jun 04, 2007 at 09:27:55AM -0400, Robert P. J. Day wrote:
> true. it's not clear that there's an overwhelming benefit of
> centralizing content that *just happens* to be the same, but i think
> there's benefit for centralizing content that must *necessarily* be
> the same.
Right. Or can usefully be made the same (see my recent-ish patch to
centralise the definitions of CONFIG_LBD/CONFIG_LSF for an example where
it made no sense to keep things separate).
> as you can see, any arch-specific ioctl.h file would simply define
> what differs from the generic, then include the asm-generic version,
> and there are at least a few of those files for which this patch would
> be perfectly appropriate. is that the sort of thing you were thinking
> about?
I think that's fine. It's a bit more clean-up-the-past than
plan-for-the-future (which was what I was trying to get at with my last
message), but it's not horribly obfuscating like the errno patches were.
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/kernel-janitors
prev parent reply other threads:[~2007-06-04 13:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 9:31 [KJ] another project or two Robert P. J. Day
2007-06-04 11:22 ` John Anthony Kazos Jr.
2007-06-04 12:00 ` Matthew Wilcox
2007-06-04 13:27 ` Robert P. J. Day
2007-06-04 13:48 ` Matthew Wilcox [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=20070604134812.GC23968@parisc-linux.org \
--to=matthew@wil.cx \
--cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.