From: Ian Abbott <abbotti@mev.co.uk>
To: Ravishankar Karkala Mallikarjunayya <ravishankarkm32@gmail.com>,
hsweeten@visionengravers.com, gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: comedi: pcmuio: fix bare use of 'unsigned'
Date: Tue, 21 Jun 2016 12:25:06 +0100 [thread overview]
Message-ID: <c1299567-d5b6-6e14-d69b-2001176a2375@mev.co.uk> (raw)
In-Reply-To: <1466504196-11352-1-git-send-email-ravishankarkm32@gmail.com>
On 21/06/16 11:16, Ravishankar Karkala Mallikarjunayya wrote:
> This fixes up a WARNING: Prefer 'unsigned int' to bare use of 'unsigned'
> found by the checkpatch.pl tool
>
> Signed-off-by: Ravishankar Karkala Mallikarjunayya <ravishankarkm32@gmail.com>
> ---
> drivers/staging/comedi/drivers/pcmuio.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/comedi/drivers/pcmuio.c b/drivers/staging/comedi/drivers/pcmuio.c
> index 7ea8130..8ad64f2 100644
> --- a/drivers/staging/comedi/drivers/pcmuio.c
> +++ b/drivers/staging/comedi/drivers/pcmuio.c
> @@ -307,7 +307,7 @@ static void pcmuio_stop_intr(struct comedi_device *dev,
>
> static void pcmuio_handle_intr_subdev(struct comedi_device *dev,
> struct comedi_subdevice *s,
> - unsigned triggered)
> + unsigned int triggered)
> {
> struct pcmuio_private *devpriv = dev->private;
> int asic = pcmuio_subdevice_to_asic(s);
>
Thanks, but this one has already been fixed in the "linux-next"
repository and in Greg's "staging" repository.
--
-=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=-
-=( Web: http://www.mev.co.uk/ )=-
prev parent reply other threads:[~2016-06-21 11:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 10:16 [PATCH] Staging: comedi: pcmuio: fix bare use of 'unsigned' Ravishankar Karkala Mallikarjunayya
2016-06-21 11:25 ` 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=c1299567-d5b6-6e14-d69b-2001176a2375@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--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).