Re: sparc: Clashing values for O_PATH and FMODE_NONOTIFY?

2014-11-20 Thread David Drysdale
On Thu, Nov 20, 2014 at 7:12 PM, Eric Paris wrote: > On Thu, 2014-11-20 at 12:12 +, David Drysdale wrote: >> [+linux-fsdevel, without the typo this time] >> >> On Wed, Nov 19, 2014 at 8:30 PM, David Miller wrote: >> > From: David Drysdale >> > Date: Tue, 18 Nov 2014 13:13:51 + >> > >>

Re: sparc: Clashing values for O_PATH and FMODE_NONOTIFY?

2014-11-20 Thread Eric Paris
On Thu, 2014-11-20 at 12:12 +, David Drysdale wrote: > [+linux-fsdevel, without the typo this time] > > On Wed, Nov 19, 2014 at 8:30 PM, David Miller wrote: > > From: David Drysdale > > Date: Tue, 18 Nov 2014 13:13:51 + > > > >> Hi folks, > >> > >> It looks like the value for O_PATH on

Re: sparc: Clashing values for O_PATH and FMODE_NONOTIFY?

2014-11-20 Thread David Drysdale
[+linux-fsdevel, without the typo this time] On Wed, Nov 19, 2014 at 8:30 PM, David Miller wrote: > From: David Drysdale > Date: Tue, 18 Nov 2014 13:13:51 + > >> Hi folks, >> >> It looks like the value for O_PATH on sparc: >> >> arch/sparc/include/uapi/asm/fcntl.h:37:#define O_PATH

Re: sparc: Clashing values for O_PATH and FMODE_NONOTIFY?

2014-11-20 Thread David Drysdale
[+linux-fsdevel, without the typo this time] On Wed, Nov 19, 2014 at 8:30 PM, David Miller da...@davemloft.net wrote: From: David Drysdale drysd...@google.com Date: Tue, 18 Nov 2014 13:13:51 + Hi folks, It looks like the value for O_PATH on sparc:

Re: sparc: Clashing values for O_PATH and FMODE_NONOTIFY?

2014-11-20 Thread Eric Paris
On Thu, 2014-11-20 at 12:12 +, David Drysdale wrote: [+linux-fsdevel, without the typo this time] On Wed, Nov 19, 2014 at 8:30 PM, David Miller da...@davemloft.net wrote: From: David Drysdale drysd...@google.com Date: Tue, 18 Nov 2014 13:13:51 + Hi folks, It looks like the

Re: sparc: Clashing values for O_PATH and FMODE_NONOTIFY?

2014-11-20 Thread David Drysdale
On Thu, Nov 20, 2014 at 7:12 PM, Eric Paris epa...@redhat.com wrote: On Thu, 2014-11-20 at 12:12 +, David Drysdale wrote: [+linux-fsdevel, without the typo this time] On Wed, Nov 19, 2014 at 8:30 PM, David Miller da...@davemloft.net wrote: From: David Drysdale drysd...@google.com Date:

Re: sparc: Clashing values for O_PATH and FMODE_NONOTIFY?

2014-11-19 Thread David Miller
From: David Drysdale Date: Tue, 18 Nov 2014 13:13:51 + > Hi folks, > > It looks like the value for O_PATH on sparc: > > arch/sparc/include/uapi/asm/fcntl.h:37:#define O_PATH 0x100 > > clashes with the arch-independent value for __FMODE_NONOTIFY: > > include/linux/fs.h:137:#define

Re: sparc: Clashing values for O_PATH and FMODE_NONOTIFY?

2014-11-19 Thread David Miller
From: David Drysdale drysd...@google.com Date: Tue, 18 Nov 2014 13:13:51 + Hi folks, It looks like the value for O_PATH on sparc: arch/sparc/include/uapi/asm/fcntl.h:37:#define O_PATH 0x100 clashes with the arch-independent value for __FMODE_NONOTIFY:

sparc: Clashing values for O_PATH and FMODE_NONOTIFY?

2014-11-18 Thread David Drysdale
Hi folks, It looks like the value for O_PATH on sparc: arch/sparc/include/uapi/asm/fcntl.h:37:#define O_PATH 0x100 clashes with the arch-independent value for __FMODE_NONOTIFY: include/linux/fs.h:137:#define FMODE_NONOTIFY ((__force fmode_t)0x100) include/linux/fs.h:2764:#define

sparc: Clashing values for O_PATH and FMODE_NONOTIFY?

2014-11-18 Thread David Drysdale
Hi folks, It looks like the value for O_PATH on sparc: arch/sparc/include/uapi/asm/fcntl.h:37:#define O_PATH 0x100 clashes with the arch-independent value for __FMODE_NONOTIFY: include/linux/fs.h:137:#define FMODE_NONOTIFY ((__force fmode_t)0x100) include/linux/fs.h:2764:#define