From: Markus Elfring <Markus.Elfring@web.de>
To: Benjamin Gaignard <benjamin.gaignard@collabora.com>,
linux-media@vger.kernel.org, linux-rockchip@lists.infradead.org,
kernel@collabora.com,
Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/2] media: videodev2: Add flags to unconditionnaly enumerate pixels formats
Date: Mon, 15 Jul 2024 16:23:01 +0200 [thread overview]
Message-ID: <3644b87d-d283-4539-aa61-263ca7a81249@web.de> (raw)
In-Reply-To: <20240712103000.16655-2-benjamin.gaignard@collabora.com>
> Add new flags to enumerate all pixels formats when calling VIDIOC_ENUM_FMT ioctl.
…
Will the word “unconditionally” be more appropriate for the next summary phrase?
Regards,
Markus
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2024-07-15 14:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 10:29 [PATCH v3 0/2] Enumerate all pixels formats Benjamin Gaignard
2024-07-12 10:29 ` [PATCH v3 1/2] media: videodev2: Add flags to unconditionnaly enumerate " Benjamin Gaignard
2024-07-12 16:31 ` Jacopo Mondi
2024-07-15 6:09 ` Benjamin Gaignard
2024-07-15 13:37 ` Jacopo Mondi
2024-07-15 13:47 ` Benjamin Gaignard
2024-07-15 14:23 ` Markus Elfring [this message]
2024-07-12 10:30 ` [PATCH v3 2/2] media: verisilicon: Use V4L2_FMT_FLAG_ENUM_ALL_FORMATS flag Benjamin Gaignard
-- strict thread matches above, loose matches on Subject: below --
2024-07-09 16:17 [PATCH v3 0/2] Enumerate all pixels formats Benjamin Gaignard
2024-07-09 16:17 ` [PATCH v3 1/2] media: videodev2: Add flags to unconditionnaly enumerate " Benjamin Gaignard
2024-07-10 12:40 ` Sebastian Fricke
2024-07-10 12:55 ` Sebastian Fricke
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=3644b87d-d283-4539-aa61-263ca7a81249@web.de \
--to=markus.elfring@web.de \
--cc=benjamin.gaignard@collabora.com \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=hverkuil-cisco@xs4all.nl \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mchehab@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