linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-ext4@vger.kernel.org, Kyle McMartin <kyle@mcmartin.ca>
Subject: Re: [PATCH] e4defrag: fix ppc build
Date: Fri, 28 Aug 2009 19:41:48 -0400	[thread overview]
Message-ID: <20090828234148.GI16732@mit.edu> (raw)
In-Reply-To: <4A9220A6.7020000@redhat.com>

On Sun, Aug 23, 2009 at 10:09:58PM -0700, Eric Sandeen wrote:
> From: Kyle McMartin <kyle@mcmartin.ca>
>
> ppc glibc seems to be missing sync_file_range, so we fell back
> to the local define, and there ppc differs as well, so the
> build was failing.
>
> Thanks to Kyle for the patch w/ the tidy solution.
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>

Thanks, applied.

					- Ted

      parent reply	other threads:[~2009-08-28 23:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-24  5:09 [PATCH] e4defrag: fix ppc build Eric Sandeen
2009-08-24 13:40 ` Greg Freemyer
2009-08-24 19:38   ` Theodore Tso
2009-08-28 23:41 ` Theodore Tso [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=20090828234148.GI16732@mit.edu \
    --to=tytso@mit.edu \
    --cc=kyle@mcmartin.ca \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@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 NNTP newsgroup(s).