From: Ian Abbott <abbotti@mev.co.uk>
To: Ravishankar Karkala Mallikarjunayya <ravishankarkm32@gmail.com>
Cc: hsweeten@visionengravers.com, gregkh@linuxfoundation.org,
geliangtang@163.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] Staging: comedi: Fix type issues in s626.c
Date: Mon, 14 Mar 2016 15:03:10 +0000 [thread overview]
Message-ID: <56E6D2AE.7050009@mev.co.uk> (raw)
In-Reply-To: <1457953584-31304-1-git-send-email-ravishankarkm32@gmail.com>
On 14/03/16 11:06, Ravishankar Karkala Mallikarjunayya wrote:
> This is a patch to the s626.c file that fixes up a type issues
> found by the checkpatch.pl tool.
>
> i.e Prefer kernel type 'u8' over 'uint8_t'
> Prefer kernel type 'u16' over 'uint16_t'
> Prefer kernel type 'u32' over 'uint32_t'
> Prefer kernel type 's16' over 'int16_t'
> Prefer kernel type 's32' over 'int32_t'
>
> Signed-off-by: Ravishankar Karkala Mallikarjunayya <ravishankarkm32@gmail.com>
> ---
> drivers/staging/comedi/drivers/s626.c | 312 +++++++++++++++++-----------------
> 1 file changed, 156 insertions(+), 156 deletions(-)
The patch would be okay, but it doesn't apply to the "staging-next"
branch of Greg's staging.git on git.kernel.org. (It doesn't apply to
the "master" branch of linux-next.git either.)
--
-=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=-
-=( Web: http://www.mev.co.uk/ )=-
prev parent reply other threads:[~2016-03-14 15:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 11:06 [PATCH 1/5] Staging: comedi: Fix type issues in s626.c Ravishankar Karkala Mallikarjunayya
2016-03-14 11:06 ` [PATCH 2/5] Staging: comedi: Fix Block comment " Ravishankar Karkala Mallikarjunayya
2016-03-14 11:06 ` [PATCH 3/5] Staging: comedi: Fix WARNING issue " Ravishankar Karkala Mallikarjunayya
2016-03-14 11:06 ` [PATCH 4/5] Staging: comedi: fix CHECK issue in ni_tio.c Ravishankar Karkala Mallikarjunayya
2016-03-14 11:06 ` [PATCH 5/5] Staging: comedi: Fix type " Ravishankar Karkala Mallikarjunayya
2016-03-14 14:39 ` Joe Perches
2016-03-14 15:03 ` Ian Abbott [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=56E6D2AE.7050009@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=geliangtang@163.com \
--cc=gregkh@linuxfoundation.org \
--cc=hsweeten@visionengravers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ravishankarkm32@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).