public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org
Subject: Re: video_device -> v4l2_devnode rename
Date: Wed, 19 Jan 2011 09:26:40 -0200	[thread overview]
Message-ID: <4D36CA70.8060204@redhat.com> (raw)
In-Reply-To: <201101190839.15175.hverkuil@xs4all.nl>

Em 19-01-2011 05:39, Hans Verkuil escreveu:
> Hi Mauro,
> 
> We want to rename video_device to v4l2_devnode. So let me know when I can
> finalize my patches and, most importantly, against which branch.
> 
> My current tree:
> 
> http://git.linuxtv.org/hverkuil/media_tree.git?a=shortlog;h=refs/heads/devnode2
> 
> tracks for_2.6.38-rc1 and should apply cleanly at the moment.

Even not being able to handle it for .38, I did a look on the proposed
changes. I'm not convinced about those renaming stuff.

By looking on other subsystems, it seems to me that video_device_register()
is a better name than any other name. Btw, by far, the use of _node for the
device registration on Linux kernel is not usual at all:

$ git grep -e "_register"  --and -e "(" --and -e "node" include |grep -v "of_mdiobus_register("
include/linux/compaction.h:extern int compaction_register_node(struct node *node);
include/linux/compaction.h:static inline int compaction_register_node(struct node *node)
include/linux/swap.h:extern int scan_unevictable_register_node(struct node *node);
include/linux/swap.h:static inline int scan_unevictable_register_node(struct node *node)

There are only 2 functions using it. On those, the "node" at the function 
register name is due to "struct node", and they likely make sense.

A seek for *register*device or *device*register patterns show a lot:

$ git grep -e "_register_device"  --and -e "("  include|wc -l
28

$ git grep -e "_device_register"  --and -e "("  include|wc -l
32

Basically, what I'm trying to say is that, on all subsystems, the function that creates
the devices is called *register*device or *device*register.

Why should we adopt anything different than the kernel convention for V4L2?

Cheers,
Mauro

  parent reply	other threads:[~2011-01-19 11:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-19  7:39 video_device -> v4l2_devnode rename Hans Verkuil
2011-01-19 10:59 ` Mauro Carvalho Chehab
2011-01-19 11:53   ` Hans Verkuil
2011-01-19 12:02     ` Mauro Carvalho Chehab
2011-01-19 11:26 ` Mauro Carvalho Chehab [this message]
2011-01-19 11:59   ` Hans Verkuil
2011-01-19 12:17     ` Mauro Carvalho Chehab

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=4D36CA70.8060204@redhat.com \
    --to=mchehab@redhat.com \
    --cc=hverkuil@xs4all.nl \
    --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