public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: "Figo.zhang" <figo1802@gmail.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Laurent Pinchart <laurent.pinchart@skynet.be>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	akpm@linux-foundation.org
Subject: Re: [PATCH]V4L:some v4l drivers have error for video_register_device
Date: Fri, 05 Jun 2009 10:51:36 +0800	[thread overview]
Message-ID: <1244170296.4603.17.camel@myhost> (raw)
In-Reply-To: <5143.62.70.2.252.1244107655.squirrel@webmail.xs4all.nl>

On Thu, 2009-06-04 at 11:27 +0200, Hans Verkuil wrote:
> > On Thu, 2009-06-04 at 11:18 +0200, Laurent Pinchart wrote:
> >> Hi,
> >>
> >> On Thursday 04 June 2009 06:20:07 figo.zhang wrote:
> >> > The function video_register_device() will call the
> >> > video_register_device_index(). In this function, firtly it will do
> >> some
> >> > argments check , if failed,it will return a negative number such as
> >> > -EINVAL, and then do cdev_alloc() and device_register(), if success
> >> return
> >> > zero. so video_register_device_index() canot return a a positive
> >> number.
> >> >
> >> > for example, see the drivers/media/video/stk-webcam.c (line 1325):
> >> >
> >> > err = video_register_device(&dev->vdev, VFL_TYPE_GRABBER, -1);
> >> > 	if (err)
> >> > 		STK_ERROR("v4l registration failed\n");
> >> > 	else
> >> > 		STK_INFO("Syntek USB2.0 Camera is now controlling video device"
> >> > 			" /dev/video%d\n", dev->vdev.num);
> >> >
> >> > in my opinion, it will be cleaner to do something like this:
> >> >
> >> > err = video_register_device(&dev->vdev, VFL_TYPE_GRABBER, -1);
> >> > 	if (err != 0)
> >> > 		STK_ERROR("v4l registration failed\n");
> >> > 	else
> >> > 		STK_INFO("Syntek USB2.0 Camera is now controlling video device"
> >> > 			" /dev/video%d\n", dev->vdev.num);
> >>
> >> What's the difference ? (err != 0) and (err) are identical.
> >>
> >> Best regards,
> >>
> >> Laurent Pinchart
> >
> > yes, it is the same, but it is easy for reading.
> 
> To be honest, I think '(err)' is easier to read. Unless there is some new
> CodingStyle rule I'm not aware of I see no reason for applying these
> changes.
> 
> Regards,
> 
>         Hans
> 

yes, but i found the the kernel code using the '(err != 0) or (err == 0)' is
more popular,in v4l code for example:

v4l1-compat.c  line 507
v4l2-int-device.c  line 52
arv.c   line 333
arv.c   line 844,856

videobuf-core.c  line 529,766,984,1002,1053
videobuf-dma-sg.c  line 211,222,248,350,456,671,

.....

so i dont know which style is recommended for kernel code?

Best Regards,

Figo.zhang



  reply	other threads:[~2009-06-05  2:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-04  9:27 [PATCH]V4L:some v4l drivers have error for video_register_device Hans Verkuil
2009-06-05  2:51 ` Figo.zhang [this message]
2009-06-05  6:12   ` Hans Verkuil
  -- strict thread matches above, loose matches on Subject: below --
2009-05-27  3:25 Figo.zhang
2009-06-04  4:20 ` figo.zhang
2009-06-04  9:18   ` Laurent Pinchart
2009-06-04  9:20     ` figo.zhang
2009-06-10 14:39       ` Mauro Carvalho Chehab
2009-06-04  9:31     ` figo.zhang

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=1244170296.4603.17.camel@myhost \
    --to=figo1802@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=hverkuil@xs4all.nl \
    --cc=laurent.pinchart@skynet.be \
    --cc=linux-media@vger.kernel.org \
    /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