From: Dan Carpenter <dan.carpenter@oracle.com>
To: Bharath Vedartham <linux.bhar@gmail.com>
Cc: gregkh@linuxfoundation.org, christian@lkamp.de,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: ralink-gdma: Change uint32_t to u32
Date: Fri, 22 Mar 2019 13:01:40 +0300 [thread overview]
Message-ID: <20190322100140.GL2202@kadam> (raw)
In-Reply-To: <20190321192502.GA11144@bharath12345-Inspiron-5559>
On Fri, Mar 22, 2019 at 12:55:02AM +0530, Bharath Vedartham wrote:
> This is a follow up on my previous patch. Change occurences of the
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Put this sort of information under the --- cut off below the Sign off.
> stdint type uint32_t to its shortened type u32. This fixed the checkpatch.pl warning: "Prefer u32 over uint32_t".
This line is too long. Limit it to 72 characters.
>
> Signed-off-by: Bharath Vedartham <linux.bhar@gmail.com>
> ---
^^^
regards,
dan carpenter
next prev parent reply other threads:[~2019-03-22 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 19:25 [PATCH] staging: ralink-gdma: Change uint32_t to u32 Bharath Vedartham
2019-03-22 10:01 ` Dan Carpenter [this message]
2019-03-22 12:04 ` 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=20190322100140.GL2202@kadam \
--to=dan.carpenter@oracle.com \
--cc=christian@lkamp.de \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.bhar@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