From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: "Ismail Dönmez" <ismail@pardus.org.tr>,
"Diego Calleja" <diegocg@gmail.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
"Mauro Carvalho Chehab" <mchehab@infradead.org>,
video4linux-list@redhat.com
Subject: Re: [PATCH 1/1] V4L: stk11xx, add a new webcam driver
Date: Fri, 25 May 2007 11:50:18 +0200 [thread overview]
Message-ID: <4656B15A.6030006@s5r6.in-berlin.de> (raw)
In-Reply-To: <4af2d03a0705250127j3d05cd6bkb114cad0e6ecb449@mail.gmail.com>
Jiri Slaby wrote:
> On 5/25/07, Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:
>> Ismail Dönmez wrote:
>> > On Thursday 24 May 2007 20:38:05 Diego Calleja wrote:
>> >> Maybe this is a too picky requeriment, but IMO it would be nice if the
>> >> module would be called "camera_stk11xx", or had any other prefix that gives
>> >> some meaning about what is doing. It's hard to decipher from the name when
>> >> you run lsmod.
>> >
>> > That would be too picky indeed since other camera modules have no camera_
>> > prefix like pwc,spca5xx, etc.
>>
>> Then how about adding that prefix to all of them and provide the current
>> name as module alias?
>>
>> Or at least, why not use better names for new modules?
>
> Just because modules can serve more that one interface of the device?
> (audio/mic, camera), (remote controller, dvb grabber). I didn't get
> the point of having the prefix in the name, what's the matter?
A prefix which describes the function of a driver is of course only
useful if it /correctly/ describes it. What would be /correct/? If a
driver for a audio + video capable camera supports either both audio and
video capture or only video capture, I don't see anything wrong with a
prefix like "camera".
That said, we have "modinfo" at our disposal if we spot something
nondescript in lsmod's listing.
--
Stefan Richter
-=====-=-=== -=-= ==--=
http://arcgraph.de/sr/
next prev parent reply other threads:[~2007-05-25 9:50 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 14:01 Jiri Slaby
2007-05-24 14:24 ` Markus Rechberger
2007-05-24 15:07 ` Jiri Slaby
2007-05-28 15:21 ` Markus Rechberger
2007-05-24 23:07 ` Jiri Slaby
2007-05-25 8:22 ` Stefan Richter
2007-05-25 8:30 ` Jiri Slaby
2007-05-24 17:38 ` Diego Calleja
2007-05-24 18:01 ` Ismail Dönmez
2007-05-25 8:19 ` Stefan Richter
[not found] ` <4af2d03a0705250127j3d05cd6bkb114cad0e6ecb449@mail.gmail.com>
2007-05-25 9:50 ` Stefan Richter [this message]
2007-05-28 15:00 ` Mauro Carvalho Chehab
2007-05-28 15:14 ` Markus Rechberger
2007-05-28 16:28 ` Luca Risolia
2007-05-28 16:42 ` Markus Rechberger
2007-05-28 18:57 ` Mauro Carvalho Chehab
2007-05-28 19:17 ` Markus Rechberger
2007-05-28 20:11 ` Mauro Carvalho Chehab
2007-05-28 21:30 ` Thierry Merle
2007-05-29 5:32 ` Thierry Merle
2007-05-29 14:25 ` Mauro Carvalho Chehab
2007-05-29 19:04 ` Thierry Merle
2007-05-29 19:31 ` Mauro Carvalho Chehab
2007-05-31 20:43 ` Thierry Merle
2007-06-01 23:10 ` Mauro Carvalho Chehab
2007-06-02 9:00 ` Thierry Merle
2007-06-04 18:55 ` Mauro Carvalho Chehab
2007-06-15 21:08 ` Jiri Slaby
2007-06-16 11:46 ` Thierry Merle
2007-06-16 12:07 ` Jiri Slaby
[not found] ` <200706190941.47459.oliver@neukum.org>
2007-06-19 7:44 ` Jiri Slaby
2007-05-30 19:44 ` Jiri Slaby
2007-06-01 23:00 ` Mauro Carvalho Chehab
2007-08-26 14:09 Jiri Slaby
2007-08-27 22:40 ` Andrew Morton
2007-08-28 5:33 ` Jiri Slaby
2007-08-28 5:36 ` Andrew Morton
2007-08-28 5:41 ` Jiri Slaby
2007-08-28 6:35 ` Alexander E. Patrakov
2007-11-06 7:40 ` Andrew Morton
2007-11-06 10:48 ` Jiri Slaby
2007-11-07 17:57 ` 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=4656B15A.6030006@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=akpm@linux-foundation.org \
--cc=diegocg@gmail.com \
--cc=ismail@pardus.org.tr \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=video4linux-list@redhat.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®