On Thu, Apr 23, 2015 at 10:43:29PM +0530, Chandan Rajendra wrote:
On Monday 20 Apr 2015 13:33:16 xuw2...@gmail.com wrote:
From: George Wang xuw2...@gmail.com
PPC64 arch use such following IOC values
\#define _IOC_NONE 1U
\#define _IOC_READ 2U
\#define _IOC_WRITE 4U
On Monday 20 Apr 2015 13:33:16 xuw2...@gmail.com wrote:
From: George Wang xuw2...@gmail.com
PPC64 arch use such following IOC values
\#define _IOC_NONE 1U
\#define _IOC_READ 2U
\#define _IOC_WRITE 4U
comparing to the default IOC values
\#define _IOC_NONE 0U
On Tue, Apr 21, 2015 at 10:26:23AM +0800, 王旭 wrote:
On 4/20/15 12:33 AM, xuw2...@gmail.com wrote:
From: George Wang xuw2...@gmail.com
snip
This means the value _IOW* will be negative when we store it in the int
variables. Such as the BTRFS_IOC_QGROUP_CREATE, it will be 0x4010942e
on
Thanks for review.
On Mon, Apr 20, 2015 at 10:47 PM, Eric Sandeen sand...@redhat.com wrote:
On 4/20/15 12:33 AM, xuw2...@gmail.com wrote:
From: George Wang xuw2...@gmail.com
snip
This means the value _IOW* will be negative when we store it in the int
variables. Such as the
On 4/20/15 12:33 AM, xuw2...@gmail.com wrote:
From: George Wang xuw2...@gmail.com
PPC64 arch use such following IOC values
\#define _IOC_NONE 1U
\#define _IOC_READ 2U
\#define _IOC_WRITE 4U
comparing to the default IOC values
\#define _IOC_NONE 0U
\#define
From: George Wang xuw2...@gmail.com
PPC64 arch use such following IOC values
\#define _IOC_NONE 1U
\#define _IOC_READ 2U
\#define _IOC_WRITE 4U
comparing to the default IOC values
\#define _IOC_NONE 0U
\#define _IOC_READ 2U
\#define _IOC_WRITE 1U
This means
