From: Ricardo Ribalda <ricardo.ribalda@gmail.com>
To: Nicolas Dufresne <nicolas@ndufresne.ca>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
": Ricardo Ribalda" <ribalda@chromium.org>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
tfiga@chromium.org, stable <stable@vger.kernel.org>
Subject: [PATCH 0/3] uvc: Restore old vdev name
Date: Tue, 7 Dec 2021 01:06:26 +0100 [thread overview]
Message-ID: <20211207000629.4985-1-ribalda@chromium.org> (raw)
In order to have unique entity names, we decided to change the name of
the video devices with their functionality.
This has resulted in some (all?) GUIs showing not useful names.
This patchset reverts the original patch and introduces a new one to
allow having different entity and vdev names.
Since some distros have ported the reverted patch to their stable
kernels, it would be great if we can get this sent asap, to avoid making
more people angry ;).
Ricardo Ribalda (3):
Revert "media: uvcvideo: Set unique vdev name based in type"
media: v4l2-dev.c: Allow driver-defined entity names
media: uvcvideo: Set unique entity name based in type
drivers/media/usb/uvc/uvc_driver.c | 14 +++++++++++---
drivers/media/v4l2-core/v4l2-dev.c | 4 +++-
2 files changed, 14 insertions(+), 4 deletions(-)
--
2.33.0
next reply other threads:[~2021-12-07 0:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 0:06 Ricardo Ribalda [this message]
2021-12-07 0:06 ` [PATCH 1/3] Revert "media: uvcvideo: Set unique vdev name based in type" Ricardo Ribalda
2021-12-07 0:14 ` Laurent Pinchart
2021-12-07 0:18 ` Laurent Pinchart
2021-12-07 0:06 ` [PATCH 2/3] media: v4l2-dev.c: Allow driver-defined entity names Ricardo Ribalda
2021-12-07 0:15 ` Laurent Pinchart
2021-12-07 0:06 ` [PATCH 3/3] media: uvcvideo: Set unique entity name based in type Ricardo Ribalda
2021-12-07 0:16 ` Laurent Pinchart
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=20211207000629.4985-1-ribalda@chromium.org \
--to=ricardo.ribalda@gmail.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nicolas@ndufresne.ca \
--cc=ribalda@chromium.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=stable@vger.kernel.org \
--cc=tfiga@chromium.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
all inboxes | Powered by JetHome®