From: Theodore Tso <tytso@mit.edu>
To: Greg Freemyer <greg.freemyer@gmail.com>
Cc: Eric Sandeen <sandeen@redhat.com>,
linux-ext4@vger.kernel.org, Kyle McMartin <kyle@mcmartin.ca>
Subject: Re: [PATCH] e4defrag: fix ppc build
Date: Mon, 24 Aug 2009 15:38:02 -0400 [thread overview]
Message-ID: <20090824193802.GA17684@mit.edu> (raw)
In-Reply-To: <87f94c370908240640n75bef581k5abe45d4f18c2f68@mail.gmail.com>
On Mon, Aug 24, 2009 at 09:40:51AM -0400, Greg Freemyer wrote:
> On Mon, Aug 24, 2009 at 1:09 AM, Eric Sandeen<sandeen@redhat.com> 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>
> > ---
> >
> > diff --git a/misc/e4defrag.c b/misc/e4defrag.c
>
> Eric,
>
> Which git repository holds e4defrag.c? I assume it is public.
>
e4defrag can be found in the 'master', 'next', and 'pu' branches of
the e2fsprogs repository. It's not in the 'maint' branch, so it's not
in any of the e2fsprogs 1.41.x releases. The 'master' branch contains
the in-development work that will be showing up in e2fsprogs 1.42; so
far the big things that there is the on-going merge 64-bit block
number support, and e4defrag.
- Ted
next prev parent reply other threads:[~2009-08-24 19:38 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 [this message]
2009-08-28 23:41 ` Theodore Tso
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=20090824193802.GA17684@mit.edu \
--to=tytso@mit.edu \
--cc=greg.freemyer@gmail.com \
--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).