public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Benno <benjl@cse.unsw.edu.au>
Cc: Dan Aloni <da-x@colinux.org>,
	Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Generation of *.s files from *.S files in kbuild
Date: Fri, 13 Aug 2004 07:04:24 +0200	[thread overview]
Message-ID: <20040813050424.GA7417@mars.ravnborg.org> (raw)
In-Reply-To: <20040813003743.GF30576@cse.unsw.edu.au>

On Fri, Aug 13, 2004 at 10:37:43AM +1000, Benno wrote:
> 
> The solution is fairly striaght forward -- just change the suffixes,
> the problem is exactly how to change them. I would propose changing it
> such that was stick with "vmlinux.lds.S" and have it generate "vmlinux.lds"
> 
> This would require the fewest changes to implement, just
> 1/ change %.s %.S rule to %.lds %.lds.S
> 2/ change the link flags from "-T vmlinux.lds.s" -> "-T vmlinux.lds"

I agree with this approach, and see no defencies.

Care to send two patches.
One that do what you suggest for i386, and another that cover the rest
of the architectures?

	Sam

  reply	other threads:[~2004-08-13  5:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-12 19:25 Generation of *.s files from *.S files in kbuild Dan Aloni
2004-08-13  0:37 ` Benno
2004-08-13  5:04   ` Sam Ravnborg [this message]
2004-08-13  8:09     ` [PATCH 1/2] " Dan Aloni
2004-08-13  9:24       ` [PATCH 1/2] #2 (Generation of *.s files from *.S files in kbuild) Dan Aloni
2004-08-13 18:33         ` Sam Ravnborg
2004-08-13 19:09           ` Dan Aloni
2004-08-13 19:17             ` Sam Ravnborg
2004-08-14 19:46           ` [PATCH] [#3 1/2] Generate vmlinux.lds instead of vmlinux.lds.s Dan Aloni
2004-08-15 18:35             ` Sam Ravnborg
2004-08-14 19:49           ` [PATCH] [#3 2/2] " Dan Aloni
2004-08-13  8:12     ` Generation of *.s files from *.S files in kbuild Dan Aloni

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=20040813050424.GA7417@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=benjl@cse.unsw.edu.au \
    --cc=da-x@colinux.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox