From: Stefan Wahren <wahrenst@gmx.net>
To: Michael Kupfer <michael.kupfer@fau.de>,
eric@anholt.net, bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Cc: Kay Friedrich <kay.friedrich@fau.de>, linux-kernel@i4.cs.fau.de
Subject: Re: [PATCH] staging/vc04_services/bcm2835-camera: distinct numeration and names for devices
Date: Wed, 4 Dec 2019 20:37:45 +0100 [thread overview]
Message-ID: <174ce1ac-157d-f943-4d3d-54c92ad82fca@gmx.net> (raw)
In-Reply-To: <20191204114814.26252-1-michael.kupfer@fau.de>
Hi Michael,
Am 04.12.19 um 12:48 schrieb Michael Kupfer:
> Create a static atomic counter for numerating cameras.
> Use the Media Subsystem Kernel Internal API to create distinct
> device-names, so that the camera-number (given by the counter)
> matches the camera-name.
>
> Co-developed-by: Kay Friedrich <kay.friedrich@fau.de>
> Signed-off-by: Kay Friedrich <kay.friedrich@fau.de>
> Signed-off-by: Michael Kupfer <michael.kupfer@fau.de>
this is a functional change. Please send this patch to Nicolas Saenz
Julienne the new BCM2835 maintainer and the Video4Linux guys (Mauro and
Hans) and the linux media mailing list.
Regards
Stefan
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-12-04 19:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 11:48 [PATCH] staging/vc04_services/bcm2835-camera: distinct numeration and names for devices Michael Kupfer
2019-12-04 19:37 ` Stefan Wahren [this message]
2019-12-04 19:40 ` Nicolas Saenz Julienne
2019-12-06 8:54 Michael Kupfer
2019-12-06 8:54 ` Michael Kupfer
2019-12-06 8:54 ` Michael Kupfer
2020-01-10 13:25 ` Hans Verkuil
2020-01-10 13:25 ` Hans Verkuil
2020-01-10 13:25 ` Hans Verkuil
2020-01-10 14:35 ` Dave Stevenson
2020-01-10 14:35 ` Dave Stevenson
2020-01-10 14:35 ` Dave Stevenson
2020-01-10 14:49 ` Hans Verkuil
2020-01-10 14:49 ` Hans Verkuil
2020-01-10 14:49 ` Hans Verkuil
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=174ce1ac-157d-f943-4d3d-54c92ad82fca@gmx.net \
--to=wahrenst@gmx.net \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=eric@anholt.net \
--cc=kay.friedrich@fau.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@i4.cs.fau.de \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=michael.kupfer@fau.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.