Re: [PATCH v18 00/22] Richacls (Core and Ext4)

2016-03-21 Thread Michael Adam
On 2016-03-15 at 21:17 +0100, Volker Lendecke wrote: > On Tue, Mar 15, 2016 at 08:45:14AM -0700, Jeremy Allison wrote: > > On Tue, Mar 15, 2016 at 12:11:03AM -0700, Christoph Hellwig wrote: > > > People have long learned that we only have 'alloc' permissions. Any > > > model that mixes allow and

Re: [PATCH v18 00/22] Richacls (Core and Ext4)

2016-03-21 Thread Michael Adam
On 2016-03-15 at 21:17 +0100, Volker Lendecke wrote: > On Tue, Mar 15, 2016 at 08:45:14AM -0700, Jeremy Allison wrote: > > On Tue, Mar 15, 2016 at 12:11:03AM -0700, Christoph Hellwig wrote: > > > People have long learned that we only have 'alloc' permissions. Any > > > model that mixes allow and

Re: [RFC 13/15] kernel: time: change inode_timespec to timespec64

2016-01-07 Thread Michael Adam
Hi, the patch contains a conflict resolution artifact.. Cheers - Michael On 2016-01-06 at 21:36 -0800, Deepa Dinamani wrote: > Substitute inode_timespec aliases with timespec64. > Since CONFIG_FS_USES_64BIT_TIME is enabled, internally > all inode_timespec references are using timespec64 >

Re: [RFC 13/15] kernel: time: change inode_timespec to timespec64

2016-01-07 Thread Michael Adam
Hi, the patch contains a conflict resolution artifact.. Cheers - Michael On 2016-01-06 at 21:36 -0800, Deepa Dinamani wrote: > Substitute inode_timespec aliases with timespec64. > Since CONFIG_FS_USES_64BIT_TIME is enabled, internally > all inode_timespec references are using timespec64 >