mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Russell King <rmk@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.19-pre6 dead Makefile entries
Date: Sun, 07 Apr 2002 21:26:06 +1000	[thread overview]
Message-ID: <27869.1018178766@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Sun, 07 Apr 2002 12:11:32 +0100." <20020407121132.E30048@flint.arm.linux.org.uk>

On Sun, 7 Apr 2002 12:11:32 +0100, 
Russell King <rmk@arm.linux.org.uk> wrote:
>On Sun, Apr 07, 2002 at 09:01:39PM +1000, Keith Owens wrote:
>> lib/Makefile                    crc32.o
>
>crc32.c seems to exist in linux/lib/ in 2.5.7 and 2.5.8-pre2

But not in 2.4.19-pre6.  Given an object which has no source, it could
be dead, a typing error or a placeholder for future work.  There is no
way to tell which, most are dead entries.

I don't object to placeholder entries ("will be back ported from 2.5
one day" or "is only used in ia64") as long as they are commented out
until the source also exists.  In this case, crc32 is required for ia64
on 2.4 kernels and we have a broken merge.  The Makefile was updated
from the ia64 patch but the source was not.  In 2.5 everybody uses
crc32.  Best fix is to delete crc32 from 2.4 Makefiles and add it only
in the ia64 patch.


  reply	other threads:[~2002-04-07 11:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-07 11:01 Keith Owens
2002-04-07 11:11 ` Russell King
2002-04-07 11:26   ` Keith Owens [this message]
2002-04-07 13:52 ` [patch] " Urban Widmark
2002-04-07 20:55   ` James H. Cloos Jr.
2002-04-08  8:46     ` Urban Widmark
2002-04-09  0:04 ` Greg KH
2002-04-07 17:52 Matt_Domsch
2002-04-07 23:41 ` Keith Owens

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=27869.1018178766@ocs3.intra.ocs.com.au \
    --to=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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®