From: Christoph Hellwig <hch@lst.de>
To: xfs-masters@oss.sgi.com
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [xfs-masters] Re: linux-next: Tree for June 24 (XFS x2)
Date: Thu, 26 Jun 2008 10:17:52 +0200 [thread overview]
Message-ID: <20080626081752.GA7462@lst.de> (raw)
In-Reply-To: <4861A4E8.1060101@sgi.com>
The patch looks good as an iterim fix. With the pending conversion
to the generic ACL code the handlers for the ACLs will move to xfs_acl.c
and solve this, too.
next prev parent reply other threads:[~2008-06-26 8:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-24 7:56 linux-next: Tree for June 24 Stephen Rothwell
2008-06-24 11:51 ` [BUG] linux-next: Tree for June 24 - kernel panic at tg3_reset_hw() on x86_64 Kamalesh Babulal
[not found] ` <20080624175612.cdf29651.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2008-06-24 17:53 ` [BUILD-FAILURE] linux-next: Tree for June 24 - missing files in drivers/media/dvb/ Kamalesh Babulal
2008-06-25 3:28 ` Stephen Rothwell
2008-06-25 3:48 ` Stephen Rothwell
2008-06-29 11:43 ` Mauro Carvalho Chehab
2008-06-29 12:35 ` Stephen Rothwell
2008-06-25 3:31 ` Stephen Rothwell
2008-06-25 0:18 ` linux-next: Tree for June 24 (XFS x2) Randy Dunlap
2008-06-25 0:37 ` [xfs-masters] " Dave Chinner
2008-06-25 1:31 ` Timothy Shimmin
2008-06-25 1:52 ` Timothy Shimmin
2008-06-26 8:17 ` Christoph Hellwig [this message]
2008-06-27 7:26 ` Stephen Rothwell
2008-06-25 2:01 ` Lachlan McIlroy
2008-06-25 3:43 ` Dave Chinner
2008-06-27 13:23 ` Christoph Hellwig
2008-07-16 7:19 ` Christoph Hellwig
2008-07-17 5:26 ` Timothy Shimmin
2008-07-17 8:28 ` Stephen Rothwell
2008-06-27 13:20 ` Christoph Hellwig
2008-06-25 0:24 ` linux-next: Tree for June 24 (ivtv) Randy Dunlap
2008-06-25 6:05 ` Hans Verkuil
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=20080626081752.GA7462@lst.de \
--to=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=xfs-masters@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;
as well as URLs for NNTP newsgroup(s).