From: Stefan Wahren <stefan.wahren@i2se.com>
To: Madhumitha Prabakaran <madhumithabiw@gmail.com>,
eric@anholt.net, gregkh@linuxfoundation.org,
f.fainelli@gmail.com, rjui@broadcom.com, sbranden@broadcom.com,
bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: vc04_services: Fix kernel type 'u32' over 'uint32_t'
Date: Wed, 15 May 2019 12:03:52 +0200 [thread overview]
Message-ID: <43fc8207-6b5b-1caa-3d19-f44074fffd0b@i2se.com> (raw)
In-Reply-To: <20190514160207.11573-1-madhumithabiw@gmail.com>
Hi Madhumitha,
On 14.05.19 18:02, Madhumitha Prabakaran wrote:
> Fix the warning issued by checkpatch
> Prefer kernel type 'u32' over 'uint32_t'
grepping the sources within vc04_services shows a lot more occurences.
I suggest to fix this style issue at least for the whole camera driver
and name the patch like
staging: bcm2835-camera: prefer kernel types
Regards
Stefan
>
> Signed-off-by: Madhumitha Prabakaran <madhumithabiw@gmail.com>
> ---
> drivers/staging/vc04_services/bcm2835-camera/mmal-msg.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/vc04_services/bcm2835-camera/mmal-msg.h b/drivers/staging/vc04_services/bcm2835-camera/mmal-msg.h
> index d1c57edbe2b8..90793c9f9a0f 100644
> --- a/drivers/staging/vc04_services/bcm2835-camera/mmal-msg.h
> +++ b/drivers/staging/vc04_services/bcm2835-camera/mmal-msg.h
> @@ -309,7 +309,7 @@ struct mmal_msg_port_parameter_set {
> u32 port_handle; /* port */
> u32 id; /* Parameter ID */
> u32 size; /* Parameter size */
> - uint32_t value[MMAL_WORKER_PORT_PARAMETER_SPACE];
> + u32 value[MMAL_WORKER_PORT_PARAMETER_SPACE];
> };
>
> struct mmal_msg_port_parameter_set_reply {
> @@ -331,7 +331,7 @@ struct mmal_msg_port_parameter_get_reply {
> u32 status; /* Status of mmal_port_parameter_get call */
> u32 id; /* Parameter ID */
> u32 size; /* Parameter size */
> - uint32_t value[MMAL_WORKER_PORT_PARAMETER_SPACE];
> + u32 value[MMAL_WORKER_PORT_PARAMETER_SPACE];
> };
>
> /* event messages */
prev parent reply other threads:[~2019-05-15 10:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 16:02 Madhumitha Prabakaran
2019-05-15 10:03 ` Stefan Wahren [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=43fc8207-6b5b-1caa-3d19-f44074fffd0b@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devel@driverdev.osuosl.org \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=madhumithabiw@gmail.com \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.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
all inboxes | Powered by JetHome®