public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Kaz Kojima <kkojima@rr.iij4u.or.jp>
To: drepper@redhat.com
Cc: libc-hacker@sources.redhat.com
Subject: Re: [PATCH] Fix SH build
Date: Sun, 17 Jun 2007 21:49:00 -0000	[thread overview]
Message-ID: <20070618.064859.56348516.kkojima@rr.iij4u.or.jp> (raw)
In-Reply-To: <467564E2.3050808@redhat.com>

> I've added all the patches.

Thanks!

> What about this SH stat patch?

[PATCH] fix __fxstatat64 function
http://sources.redhat.com/ml/libc-alpha/2007-06/msg00070.html?

I guess this isn't needed anymore because SH kernel header was fixed
http://www.mail-archive.com/git-commits-head@vger.kernel.org/msg11498.html

Regards,
	kaz

      reply	other threads:[~2007-06-17 21:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-10  4:32 Kaz Kojima
2007-06-16 22:08 ` Kaz Kojima
2007-06-17 16:44   ` Ulrich Drepper
2007-06-17 21:49     ` Kaz Kojima [this message]

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=20070618.064859.56348516.kkojima@rr.iij4u.or.jp \
    --to=kkojima@rr.iij4u.or.jp \
    --cc=drepper@redhat.com \
    --cc=libc-hacker@sources.redhat.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).