Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: linux-mips@linux-mips.org, ica2_ts@csv.ica.uni-stuttgart.de
Subject: Re: [PATCH, 2.4] Fix bad check_gcc order for mips64, make offset.h creation more robust
Date: Mon, 22 Mar 2004 21:09:06 +0100	[thread overview]
Message-ID: <20040322200906.GA19051@linux-mips.org> (raw)
In-Reply-To: <20040322.160627.41628364.nemoto@toshiba-tops.co.jp>

On Mon, Mar 22, 2004 at 04:06:27PM +0900, Atsushi Nemoto wrote:

> Could you remember this two months old patch?

Sorry ...  Applied.

  Ralf

  reply	other threads:[~2004-03-22 20:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20031021232555Z8225529-1272+8229@linux-mips.org>
2003-11-05  8:17 ` define check_gcc before used (Re: CVS Update@-mips.org: linux) Atsushi Nemoto
2004-03-22  7:06   ` [PATCH, 2.4] Fix bad check_gcc order for mips64, make offset.h creation more robust Atsushi Nemoto
2004-03-22 20:09     ` Ralf Baechle [this message]
2004-01-22  4:07 Thiemo Seufer

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=20040322200906.GA19051@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=ica2_ts@csv.ica.uni-stuttgart.de \
    --cc=linux-mips@linux-mips.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