From: Greg KH <gregkh@linuxfoundation.org>
To: Bharath Vedartham <linux.bhar@gmail.com>
Cc: philipp.panzer@fau.de, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] staging: ralink-gdma: Use u32 over uint32_t
Date: Sun, 24 Mar 2019 09:58:33 +0100 [thread overview]
Message-ID: <20190324085833.GA21912@kroah.com> (raw)
In-Reply-To: <20190323154648.GA10634@bharath12345-Inspiron-5559>
On Sat, Mar 23, 2019 at 09:16:48PM +0530, Bharath Vedartham wrote:
> Fixes the checkpatch.pl warning: "Prefer u32 over uint32_t"
>
> Signed-off-by: Bharath Vedartham <linux.bhar@gmail.com>
> ---
> Changes since v3
> - Fixed allignment issues.
> - Submitted a seperate patch to change unsigned
> to unsigned int.
> - One of the allignments crosses 80 characters in a line
> but I feel that we may loose readability if we try to reduce
> the characters in the line.
> ---
> drivers/staging/ralink-gdma/ralink-gdma.c | 14 ++++++--------
> 1 file changed, 6 insertions(+), 8 deletions(-)
This patch does not apply to my staging-testing branch at all :(
next prev parent reply other threads:[~2019-03-24 8:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-23 15:46 [PATCH v4] staging: ralink-gdma: Use u32 over uint32_t Bharath Vedartham
2019-03-24 8:58 ` Greg KH [this message]
2019-03-24 9:39 ` Bharath Vedartham
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=20190324085833.GA21912@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.bhar@gmail.com \
--cc=philipp.panzer@fau.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.