From: Hans de Goede <hdegoede@redhat.com>
To: Shayenne da Luz Moura <shayenneluzmoura@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Michael Thayer <michael.thayer@oracle.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
outreachy-kernel@googlegroups.com
Subject: Re: [PATCH 0/2] staging: vboxvideo: Remove chekpatch issues
Date: Fri, 26 Oct 2018 12:34:33 +0200 [thread overview]
Message-ID: <e59aeb92-b2f9-ae8d-f910-4410ba9c732a@redhat.com> (raw)
In-Reply-To: <cover.1540490962.git.shayenneluzmoura@gmail.com>
Hi,
On 25-10-18 21:40, Shayenne da Luz Moura wrote:
> This series cleans the following checkpatch.pl issues:
>
> CHECK: Prefer kernel type 'u32' over 'uint32_t'
> CHECK: Avoid using bool structure members because of possible alignment issues
>
> Shayenne da Luz Moura (2):
> staging: vboxvideo: Change uint32_t to u32
> staging: vboxvideo: Use unsigned int instead bool
Why am I receiving only the cover letter of this series? Please resend
so that I get all the patches.
Also at least the first patch is wrong, the drm headers use uint32_t
in the prototype definition of the callback functions we are defining,
so the vboxvideo code should use the same even if the compiler does not
warn about the callback implementation having different parameter types
in this case.
Regards,
Hans
>
> drivers/staging/vboxvideo/vbox_drv.h | 14 +++++++-------
> drivers/staging/vboxvideo/vbox_mode.c | 2 +-
> drivers/staging/vboxvideo/vboxvideo_guest.h | 2 +-
> 3 files changed, 9 insertions(+), 9 deletions(-)
>
prev parent reply other threads:[~2018-10-26 10:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-25 19:40 Shayenne da Luz Moura
2018-10-26 10:34 ` Hans de Goede [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=e59aeb92-b2f9-ae8d-f910-4410ba9c732a@redhat.com \
--to=hdegoede@redhat.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.thayer@oracle.com \
--cc=outreachy-kernel@googlegroups.com \
--cc=shayenneluzmoura@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
all inboxes | Powered by JetHome®