All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Valdis.Kletnieks@vt.edu
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: simplify numerous param.h's by including <asm-generic/param.h>?
Date: Wed, 30 Dec 2009 03:17:47 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0912300316070.11919@localhost> (raw)
In-Reply-To: <9192.1262110147@localhost>

On Tue, 29 Dec 2009, Valdis.Kletnieks@vt.edu wrote:

> On Tue, 29 Dec 2009 12:30:23 EST, "Robert P. J. Day" said:
> >
> >   a brief perusal of the numerous param.h files under
> > arch/<arch>/include/asm shows that most of them could be replaced with
> > a simple
> >
> >   #include <asm-generic/param.h>
>
> >   worth doing?  not worth doing?
>
> Anytime you can fix "You are in a twisty maze of #include files, all
> subtly different" issues, it is a Good Thing.
>
> Thanks for all the de-cruftifying efforts you've made.

  ok, so i'm assuming there's no legitimate objection to having
numerous arch-specific param.h files simply refer to
<asm-generic/param.h> if that's appropriate.  i'll submit individual
patches on a per-arch basis to the appropriate MLs.

rday
--

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

            Linux Consulting, Training and Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================

      reply	other threads:[~2009-12-30  8:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-29 17:30 simplify numerous param.h's by including <asm-generic/param.h>? Robert P. J. Day
2009-12-29 18:09 ` Valdis.Kletnieks
2009-12-30  8:17   ` 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.2.00.0912300316070.11919@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=Valdis.Kletnieks@vt.edu \
    --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 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.