mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Timothy Shimmin <tes@sgi.com>
Cc: xfs-masters@oss.sgi.com, linux-next@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	"Alexander Beregalov" <a.beregalov@gmail.com>
Subject: Re: [xfs-masters] Re: linux-next: Tree for June 24 (XFS x2)
Date: Fri, 27 Jun 2008 17:26:14 +1000	[thread overview]
Message-ID: <20080627172614.83a604e4.sfr@canb.auug.org.au> (raw)
In-Reply-To: <4861A4E8.1060101@sgi.com>

[-- Attachment #1: Type: text/plain, Size: 1343 bytes --]

On Wed, 25 Jun 2008 11:52:40 +1000 Timothy Shimmin <tes@sgi.com> wrote:
>
> So we could move up the acl defines in xfs_acl.h.
> Unless Christoph wants some other rearrangement...
> 
> Index: 2.6.x-xfs-quilt/fs/xfs/xfs_acl.h
> ===================================================================
> --- 2.6.x-xfs-quilt.orig/fs/xfs/xfs_acl.h	2008-06-25 10:46:42.000000000 +1000
> +++ 2.6.x-xfs-quilt/fs/xfs/xfs_acl.h	2008-06-25 11:45:25.221045485 +1000
> @@ -46,6 +46,8 @@ typedef struct xfs_acl {
>  #define SGI_ACL_FILE_SIZE	(sizeof(SGI_ACL_FILE)-1)
>  #define SGI_ACL_DEFAULT_SIZE	(sizeof(SGI_ACL_DEFAULT)-1)
>  
> +#define _ACL_TYPE_ACCESS	1
> +#define _ACL_TYPE_DEFAULT	2
>  
>  #ifdef CONFIG_XFS_POSIX_ACL
>  
> @@ -66,8 +68,6 @@ extern int xfs_acl_vset(bhv_vnode_t *, v
>  extern int xfs_acl_vget(bhv_vnode_t *, void *, size_t, int);
>  extern int xfs_acl_vremove(bhv_vnode_t *, int);
>  
> -#define _ACL_TYPE_ACCESS	1
> -#define _ACL_TYPE_DEFAULT	2
>  #define _ACL_PERM_INVALID(perm)	((perm) & ~(ACL_READ|ACL_WRITE|ACL_EXECUTE))
>  
>  #define _ACL_INHERIT(c,m,d)	(xfs_acl_inherit(c,m,d))
> 

I have applied this to linux-next for today, please apply it (or
something similar) to the xfs tree soon.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2008-06-27  7:26 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
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
2008-06-27  7:26         ` Stephen Rothwell [this message]
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=20080627172614.83a604e4.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=a.beregalov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=tes@sgi.com \
    --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

all inboxes | Powered by JetHome®