From: Oleg Verych <olecom@flower.upol.cz>
To: Sam Ravnborg <sam@ravnborg.org>, Rusty Russell <rusty@rustcorp.com.au>
Cc: kbuild-devel@lists.sourceforge.net, LKML <linux-kernel@vger.kernel.org>
Subject: Removing of dummy asm-offset files (Re: [patch 02/03] kbuild, asm-values: successor of asm-offsets)
Date: Wed, 13 Jun 2007 10:55:14 +0200 [thread overview]
Message-ID: <20070613085514.GI7266@flower.upol.cz> (raw)
In-Reply-To: <20070612234558.782193000@flower.upol.cz>
[]
> +# legacy asm-offsets support (FIXME: convert all archs and remove this)
> +old = $(shell test -e $(srctree)/arch/$(ARCH)/kernel/asm-offsets.c && echo yes)
> +ifeq ($(old),yes)
> + asm-values =asm-offsets
> +else
> + asm-values =asm-values
One more test here, and files like
|-*-
olecom@flower:/mnt/work/pc/kernel.org/linux-2.6.22-rc4-mm2$ <
arch/sparc64/kernel/asm-offsets.c dd
/* Dummy asm-offsets.c file. Required by kbuild and ready to be used - hint! */
|-*-
can be removed.
____
next prev parent reply other threads:[~2007-06-13 8:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 23:36 [patch 00/03] kbuild, asm-values: not only offsets, not only for $ARCH Oleg Verych
2007-06-12 23:36 ` [patch 01/03] kbuild, asm-values: infrastructure Oleg Verych
2007-06-14 7:41 ` Oleg Verych
2007-06-14 9:12 ` Sam Ravnborg
2007-06-14 11:16 ` Need opinions on asm-offsets cleanup (Re: [patch 01/03] kbuild, asm-values: infrastructure) Oleg Verych
2007-06-14 11:23 ` Sam Ravnborg
2007-09-16 18:29 ` [patch 01/03] kbuild, asm-values: infrastructure Sam Ravnborg
2007-09-16 19:32 ` Rename asm-offsets tool or not? (Re: [patch 01/03] kbuild, asm-values: infrastructure) Oleg Verych
2007-09-16 20:12 ` Sam Ravnborg
2007-06-12 23:36 ` [patch 02/03] kbuild, asm-values: successor of asm-offsets Oleg Verych
2007-06-13 8:55 ` Oleg Verych [this message]
2007-06-12 23:36 ` [patch 03/03] kbuild, asm-values: private for lguest Oleg Verych
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=20070613085514.GI7266@flower.upol.cz \
--to=olecom@flower.upol.cz \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=sam@ravnborg.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
all inboxes | Powered by JetHome®