All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timothy Shimmin <tes@sgi.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com
Subject: Re: [GIT PULL] XFS update for 2.6.23
Date: Thu, 20 Sep 2007 17:35:25 +1000	[thread overview]
Message-ID: <46F222BD.5000001@sgi.com> (raw)
In-Reply-To: <46F16149.8080503@sandeen.net>

Hi Eric,

Thanks.
I'll add that commit along with the sparse one...
    commit f5076f1243d6007145c0a658fbe05ace6b90a33f
    Author: Christoph Hellwig <hch@infradead.org>
    Date:   Wed Sep 19 15:27:30 2007 +1000

     [XFS] fix valid but harmless sparse warning

--Tim

Eric Sandeen wrote:
> Tim Shimmin wrote:
>> Hi Linus,
>>
>> A couple of fixes for potential fs corruption.
>> And one fix to ensure that xfs_mru_cache is not
>> doing anything unless the cache has active objects.
> 
> cc: trimmed...
> 
> Seems like you should push the filestreams fix too?
> 
> http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/xfs-2.6.git;a=commitdiff;h=f4b26d9d73e38ff915720440b1c373fb239a4254
> 
> Thanks,
> 
> -Eric
> 
> p.s. just FWIW, here are the patches I'm currently carrying in F8:
> 
> linux-2.6-xfs-avoid-replaying-inode-buffer-init.patch	In for-linus
> linux-2.6-xfs-filesize-updates.patch			In for-linus
> linux-2.6-xfs-filestreams-on-demand-MRU-reaping.patch	In for-linus
> linux-2.6-xfs-fix-filestreams-free-func-cast.patch
> linux-2.6-xfs-optimize-away-dmapi-tests.patch
> linux-2.6-xfs-optimize-away-realtime-tests.patch
> linux-2.6-xfs-refactor-xfs_mountfs.patch
> linux-2.6-xfs-setfattr-32bit-compat.patch

  reply	other threads:[~2007-09-20  7:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-18 11:24 [GIT PULL] XFS update for 2.6.23 Tim Shimmin
2007-09-19 17:50 ` Eric Sandeen
2007-09-20  7:35   ` Timothy Shimmin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-09-20 10:12 Tim 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=46F222BD.5000001@sgi.com \
    --to=tes@sgi.com \
    --cc=sandeen@sandeen.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.