mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Miles Bader <miles@lsi.nec.co.jp>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg Ungerer <gerg@snapgear.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH]  v850 additions to include/linux/elf.h
Date: 28 Nov 2002 10:20:57 +0900	[thread overview]
Message-ID: <buok7iybibq.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <1038402095.6394.24.camel@irongate.swansea.linux.org.uk>

Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> > If tidying is needed, then it seems like the best thing would be to move
> > all the arch-specific stuff into the corresponding <asm/elf.h> file for
> > each architecture.
> 
> I agree entirely. So lets start with v850 8)

Okay.  I sent the previous patch to Linus and he doesn't seem to have
taken it; perhaps your suggestion will fare better.

I'd like to remain consistent with other archs though -- does anyone
want to make a patch (I guess just move all the R_... constants) for them?

-Miles
-- 
Yo mama's so fat when she gets on an elevator it HAS to go down.

  reply	other threads:[~2002-11-28  1:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-15 15:25 [PATCH]: linux-2.5.42uc1 (MMU-less support) Greg Ungerer
2002-10-15 17:16 ` Christoph Hellwig
2002-10-16 14:41   ` Greg Ungerer
2002-10-16 14:48     ` Christoph Hellwig
2002-10-16 15:36       ` Greg Ungerer
2002-11-26  7:46   ` [PATCH] Make some EXPORT_SYMBOLs dependent on CONFIG_MMU Miles Bader
2002-11-26  7:49   ` [PATCH] v850 additions to include/linux/elf.h Miles Bader
2002-11-26 15:41     ` Alan Cox
2002-11-27  1:19       ` Miles Bader
2002-11-27 13:01         ` Alan Cox
2002-11-28  1:20           ` Miles Bader [this message]
2002-10-16  5:42 ` [PATCH]: linux-2.5.42uc1 (MMU-less support) Miles Bader
2002-10-16 12:49   ` Greg Ungerer

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=buok7iybibq.fsf@mcspd15.ucom.lsi.nec.co.jp \
    --to=miles@lsi.nec.co.jp \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gerg@snapgear.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miles@gnu.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®