mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: David Miller <davem@davemloft.net>
Cc: torvalds@linux-foundation.org, alistair@devzero.co.uk,
	rjw@sisk.pl, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.28-rc1
Date: Sat, 25 Oct 2008 00:51:21 +0200	[thread overview]
Message-ID: <20081024225121.GA19759@uranus.ravnborg.org> (raw)
In-Reply-To: <20081024.153139.36591021.davem@davemloft.net>

On Fri, Oct 24, 2008 at 03:31:39PM -0700, David Miller wrote:
> From: Linus Torvalds <torvalds@linux-foundation.org>
> Date: Fri, 24 Oct 2008 08:17:53 -0700 (PDT)
> 
> > Now, _another_ part (and arguably the really core reason) of this problem 
> > is that our Makefile rules for the asm include directory is weak and 
> > unreliable in the presense of already-existing unexpected entries.
> 
> I guess we could use seperate "stamp" files to deal with this.
> 
> Along with the generated file "foo" there is a "foo.stamp" file
> that is generated with "touch" after "foo" is built.

I remember I made an attempt doing so long time ago for
the asm symlink. But why it failed for me I dunno.

We used this trick in many archs before
but as part of the header move to arch/$ARCH we have killed
almost all uses of symlink to reach certain files.

The asm symlink is only used by asm-offsett.h for most archs these
days and when I get around to it I will fix that too so we
can kill it entirely.

But first we need to move all archs headers to arch/$ARCH.
And we are getting there.

	Sam

  reply	other threads:[~2008-10-24 22:52 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-24  4:10 Linus Torvalds
2008-10-24  4:14 ` Roland Dreier
2008-10-24 18:08   ` Greg KH
2008-10-24 11:24 ` Alistair John Strachan
2008-10-24 11:45   ` Rafael J. Wysocki
2008-10-24 12:52     ` Alistair John Strachan
2008-10-24 13:13       ` Alexey Dobriyan
2008-10-24 14:56         ` git-clean [Was: Linux 2.6.28-rc1] Björn Steinbrink
2008-10-24 15:17       ` Linux 2.6.28-rc1 Linus Torvalds
2008-10-24 19:22         ` Sam Ravnborg
2008-10-24 22:31         ` David Miller
2008-10-24 22:51           ` Sam Ravnborg [this message]
2008-10-24 19:15   ` Sam Ravnborg
2008-10-24 23:44     ` Alistair John Strachan
2008-10-24 17:09 ` Matt Mackall
2008-10-24 17:54   ` Matt Mackall
2008-10-24 17:57     ` Randy Dunlap
2008-10-24 18:05       ` Fenghua Yu
2008-10-24 18:11         ` Matt Mackall
2008-10-24 22:28 ` nf_conntrack oopes on parisc/smp (was Re: Linux 2.6.28-rc1) Domenico Andreoli
2008-10-24 22:53 ` Linux 2.6.28-rc1 Tony Vroon
2008-10-24 23:01   ` Arjan van de Ven
2008-10-26 13:17     ` Tony Vroon
2008-10-30 14:26 ` 2.6.28-rc1: NVRAM being corrupted on ppc64 preventing boot (bisected) Mel Gorman
2008-10-30 20:52   ` Paul Mackerras
2008-10-30 21:05     ` Josh Boyer
2008-10-30 21:35       ` Dave Kleikamp
2008-10-31 10:36     ` Mel Gorman
2008-10-31 11:10       ` Paul Mackerras
2008-10-31 11:31         ` Mel Gorman
2008-10-31 18:36         ` Mel Gorman
2008-10-31 11:18       ` Paul Mackerras
2008-10-31 11:31         ` Benjamin Herrenschmidt
2008-10-31 11:56           ` Paul Mackerras
2008-10-31 11:32         ` Mel Gorman
2008-10-24 18:10 Linux 2.6.28-rc1 Rufus & Azrael

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=20081024225121.GA19759@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=alistair@devzero.co.uk \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=torvalds@linux-foundation.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

Powered by JetHome