From: Greg KH <gregkh@linuxfoundation.org>
To: Thimo Braker <thibmorozier@gmail.com>
Cc: labbott@redhat.com, sumit.semwal@linaro.org, arve@android.com,
iandrews@android.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] Staging: android: uapi: ion: Fixes indentation
Date: Mon, 9 May 2016 14:08:05 +0200 [thread overview]
Message-ID: <20160509120805.GA4311@kroah.com> (raw)
In-Reply-To: <1462707707-51783-1-git-send-email-thibmorozier@gmail.com>
On Sun, May 08, 2016 at 01:41:47PM +0200, Thimo Braker wrote:
> Fixes the indentation before variable names.
>
> Signed-off-by: Thimo Braker <thibmorozier@gmail.com>
> ---
> drivers/staging/android/uapi/ion.h | 20 ++++++++++----------
> drivers/staging/android/uapi/ion_test.h | 10 +++++-----
> 2 files changed, 15 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/staging/android/uapi/ion.h b/drivers/staging/android/uapi/ion.h
> index 0a8e40f..6dda8d5 100644
> --- a/drivers/staging/android/uapi/ion.h
> +++ b/drivers/staging/android/uapi/ion.h
> @@ -91,11 +91,11 @@ enum ion_heap_type {
> * Provided by userspace as an argument to the ioctl
> */
> struct ion_allocation_data {
> - size_t len;
> - size_t align;
> - unsigned int heap_id_mask;
> - unsigned int flags;
> - ion_user_handle_t handle;
> + size_t len;
> + size_t align;
> + unsigned int heap_id_mask;
> + unsigned int flags;
> + ion_user_handle_t handle;
Hm, that's not really a "fix" anywhere. There's no kernel rule that you
have to align the fields in a structure.
What "tool" told you this was necessary?
So this patch isn't needed, sorry.
thanks,
greg k-h
prev parent reply other threads:[~2016-05-09 12:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-08 11:41 [PATCH v2 1/1] Staging: android: uapi: ion: Fixes indentation Thimo Braker
2016-05-09 12:08 ` Greg KH [this message]
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=20160509120805.GA4311@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arve@android.com \
--cc=devel@driverdev.osuosl.org \
--cc=iandrews@android.com \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=thibmorozier@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;
as well as URLs for NNTP newsgroup(s).