From: "Daniel W. S. Almeida" <dwlsalmeida@gmail.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
sean@mess.org, linux-media@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: We should settle on a name for the new DVB virtual driver.
Date: Wed, 25 Mar 2020 17:00:30 -0300 [thread overview]
Message-ID: <66165ca2-1e48-2dbf-cf5b-c3b583e7d0c6@gmail.com> (raw)
It has come to my attention that this patch -
https://patchwork.linuxtv.org/patch/62494/ - has reorganized a few
directories in the media tree, pushing test drivers into their own
directory.
In an effort to reduce the amount of renaming down the line, and also to
adapt to the new structure presented above I think it is a good time to
come up with a name for the DVB virtual driver. It might also be a good
idea to move it to its own directory as well while we're at it.
My personal preference is vidvb, which is somewhat in line with the
naming scheme used by other virtual drivers for the media subsystem.
Please chime in.
Thanks.
- Daniel.
next reply other threads:[~2020-03-25 20:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 20:00 Daniel W. S. Almeida [this message]
2020-03-25 20:45 ` We should settle on a name for the new DVB virtual driver 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=66165ca2-1e48-2dbf-cf5b-c3b583e7d0c6@gmail.com \
--to=dwlsalmeida@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sean@mess.org \
--cc=skhan@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).