From: Eric Sandeen <sandeen@sandeen.net>
To: Lachlan McIlroy <lachlan@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: [GIT PULL] XFS update for 2.6.25-rc4
Date: Mon, 25 Feb 2008 23:12:57 -0800 [thread overview]
Message-ID: <47C3BBF9.8090403@sandeen.net> (raw)
In-Reply-To: <20080226064909.5457F58C4C0F@chook.melbourne.sgi.com>
Lachlan McIlroy wrote:
> Please pull from the for-linus branch:
> git pull git://oss.sgi.com:8090/xfs/xfs-2.6.git for-linus
>
> This will update the following files:
>
> fs/xfs/xfs_bit.c | 103 ++++++++++++++++++++++++++++++++++++++++++++++++++
> fs/xfs/xfs_bit.h | 27 ++-----------
> fs/xfs/xfs_rtalloc.c | 19 ++++++---
> 3 files changed, 120 insertions(+), 29 deletions(-)
what's the thought on fixing the ikeep regression for 2.6.25?
-Eric
> through these commits:
>
> commit ef8ece55d9b6825c28a5c1a4bd89b94040cb7b32
> Author: Lachlan McIlroy <lachlan@sgi.com>
> Date: Tue Feb 26 17:00:22 2008 +1100
>
> [XFS] Undo bit ops cleanup mod due to regression on 32-bit powermac
> platform.
>
> SGI-PV: 971186
> SGI-Modid: xfs-linux-melb:xfs-kern:30559a
>
> Signed-off-by: Lachlan McIlroy <lachlan@sgi.com>
>
> commit db69c915e67705daac25cad06d816c09be634de0
> Author: Lachlan McIlroy <lachlan@sgi.com>
> Date: Tue Feb 26 17:00:14 2008 +1100
>
> [XFS] Undo bit ops cleanup mod due to regression on 32-bit powermac
> platform.
>
> SGI-PV: 974005
> SGI-Modid: xfs-linux-melb:xfs-kern:30558a
>
> Signed-off-by: Lachlan McIlroy <lachlan@sgi.com>
>
>
next prev parent reply other threads:[~2008-02-26 7:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 6:49 [GIT PULL] XFS update for 2.6.25-rc4 Lachlan McIlroy
2008-02-26 7:12 ` Eric Sandeen [this message]
2008-02-26 7:32 ` Lachlan McIlroy
-- strict thread matches above, loose matches on Subject: below --
2008-02-29 3:50 Lachlan McIlroy
2008-02-29 4:12 ` Eric Sandeen
2008-02-29 4:56 ` Lachlan McIlroy
2008-02-29 5:44 ` Eric Sandeen
2008-02-29 6:41 ` Mark Goodwin
2008-02-29 6:59 ` Lachlan McIlroy
2008-02-29 7:39 ` Timothy Shimmin
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=47C3BBF9.8090403@sandeen.net \
--to=sandeen@sandeen.net \
--cc=lachlan@sgi.com \
--cc=xfs@oss.sgi.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