All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Remove macro MAXHOSTNAMELEN from <asm-generic/param.h>.
Date: Tue, 29 Dec 2009 20:03:01 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0912292002370.6803@localhost> (raw)
In-Reply-To: <20091230115610.c10599b8.sfr@canb.auug.org.au>

On Wed, 30 Dec 2009, Stephen Rothwell wrote:

> Hi Robert,
>
> On Tue, 29 Dec 2009 19:32:15 -0500 (EST) "Robert P. J. Day" <rpjday@crashcourse.ca> wrote:
> >
> > Since nothing in the entire tree makes use of this macro, remove
> > it. This removal should eventually propagate to all of the
> > arch-specific param.h files.
>
> Except if the only place this is picked up by glibc is the kernel
> header files, then it will disappear from user mode and some
> packages may break.

  true, but this still takes me back to my original observation -- why
is this macro being defined in a kernel header file if the kernel
itself has absolutely no interest in it and doesn't use it in any way?

  if glibc wants it, it might as well define it.

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  1:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-30  0:32 [PATCH] Remove macro MAXHOSTNAMELEN from <asm-generic/param.h> Robert P. J. Day
2009-12-30  0:56 ` Stephen Rothwell
2009-12-30  1:03   ` Robert P. J. Day [this message]
2009-12-30  2:05     ` Vikram Dhillon

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.0912292002370.6803@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.