public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Stultz <john.stultz@linaro.org>
To: Joe Perches <joe@perches.com>, Seunghun Lee <waydi1@gmail.com>
Cc: greg@kroah.com, swetland@google.com, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org, Colin Cross <ccross@android.com>
Subject: Re: [PATCH] staging : android : uapi : fix coding style
Date: Wed, 16 Apr 2014 09:36:13 -0700	[thread overview]
Message-ID: <534EB17D.6090307@linaro.org> (raw)
In-Reply-To: <1397659190.32088.4.camel@joe-AO722>

On 04/16/2014 07:39 AM, Joe Perches wrote:
> On Wed, 2014-04-16 at 23:27 +0900, Seunghun Lee wrote:
>> This patch fix checkpatch.pl warnings and errors.
> []
>> diff --git a/drivers/staging/android/uapi/binder.h b/drivers/staging/android/uapi/binder.h
> []
>> @@ -169,7 +169,7 @@ struct binder_ptr_cookie {
>>  struct binder_handle_cookie {
>>  	__u32 handle;
>>  	binder_uintptr_t cookie;
>> -} __attribute__((packed));
>> +} __packed;
> If this .h file is meant to be a user-space #include,
> then it should not use the kernel specific __packed
> but keep the __attribute__((packed))

Agreed.

> It does use __u32 though and that's generally
> kernel specific.

Hmm. Theres a ton of __u32 usage in include/uapi/*  as well as typedefs
for it too.
include/uapi/asm-generic/int-l64.h:typedef unsigned int __u32;
include/uapi/asm-generic/int-ll64.h:typedef unsigned int __u32;

> John?  Does any of these binder uapi files need a
> bit more sorting out?
I suspect this is ok, but Cc'ing Colin to give him a heads up, as it
would probably cause trouble w/ their libc headers first.


thanks
-john

  reply	other threads:[~2014-04-16 16:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-16 14:27 [PATCH] staging : android : uapi : fix coding style Seunghun Lee
2014-04-16 14:39 ` Joe Perches
2014-04-16 16:36   ` John Stultz [this message]
2014-04-16 16:54     ` Colin Cross
2014-04-16 14:44 ` Dan Carpenter
2014-04-16 15:27   ` earl
  -- strict thread matches above, loose matches on Subject: below --
2014-04-16 15:39 [PATCH] staging: android: uapi: " Seunghun Lee

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=534EB17D.6090307@linaro.org \
    --to=john.stultz@linaro.org \
    --cc=ccross@android.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=greg@kroah.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=swetland@google.com \
    --cc=waydi1@gmail.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