public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Timothy Shimmin <tes@sgi.com>
To: torvalds@linux-foundation.org
Cc: Andrew Morton <akpm@linux-foundation.org>, xfs-oss <xfs@oss.sgi.com>
Subject: [GIT PULL] XFS lockdep fix for 2.6.22
Date: Fri, 29 Jun 2007 19:25:05 +1000	[thread overview]
Message-ID: <4684CFF1.70700@sgi.com> (raw)

Hi Linus,

We have a patch to help for lockdep annotations which were
busted in XFS.
We still have more work to go - on to next lockdep warning.

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_inode.h    |   15 +++++++++------
  fs/xfs/xfs_vnodeops.c |    4 ++--
  2 files changed, 11 insertions(+), 8 deletions(-)

through these commits:

commit 09ff7bd79164131cc041777e291a951a7adb8ab4
Author: David Chinner <dgc@sgi.com>
Date:   Fri Jun 29 17:26:09 2007 +1000

     [XFS] Fix lockdep annotations for xfs_lock_inodes

     SGI-PV: 967035
     SGI-Modid: xfs-linux-melb:xfs-kern:29026a

     Signed-off-by: David Chinner <dgc@sgi.com>
     Signed-off-by: Tim Shimmin <tes@sgi.com>

--Tim

                 reply	other threads:[~2007-06-29  9:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4684CFF1.70700@sgi.com \
    --to=tes@sgi.com \
    --cc=akpm@linux-foundation.org \
    --cc=torvalds@linux-foundation.org \
    --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