From: Jonathan Corbet <corbet@lwn.net>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
mchehab@kernel.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
torvalds@linux-foundation.org, randy.dunlap@oracle.com,
paulmck@kernel.org, markus.heiser@darmarIT.de
Subject: Re: [PATCH]upi:media: Added rest of the Generic Error Codes to the existing list
Date: Mon, 07 Aug 2023 12:12:00 -0600 [thread overview]
Message-ID: <875y5q67tb.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230807045212.32489-2-unixbhaskar@gmail.com>
Bhaskar Chowdhury <unixbhaskar@gmail.com> writes:
> Added rest of the Generic Error Codes to the existing list of codes.
>
> cc: torvalds@linux-foundation.org
> cc: randy.dunlap@oracle.com
> cc: paulmck@kernel.org
> cc: corbet@lwn.net
> cc: markus.heiser@darmarIT.de
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
> ---
> There is a "moreutils" package across the Linux distribution, if you
> installed it and that package has a binary name "errno",if you run it with
> "-l" or "--list" option, it will show all the error codes.In my system, while
> running it shows me precisely, 134 of such codes.YMMV
>
> .../userspace-api/media/gen-errors.rst | 479 ++++++++++++++++++
> 1 file changed, 479 insertions(+)
This document is a list of errors that can be returned by media drivers,
with a focus on what those errors mean in the media context. What is
the point of stuffing it full of error numbers that media drivers will
never return, along with generic, one-line descriptions? I'll defer to
the media folks on this, but I don't think this helps their users.
Thanks,
jon
next prev parent reply other threads:[~2023-08-07 18:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 4:33 Bhaskar Chowdhury
2023-08-07 18:12 ` Jonathan Corbet [this message]
2023-08-18 7:37 ` 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=875y5q67tb.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=markus.heiser@darmarIT.de \
--cc=mchehab@kernel.org \
--cc=paulmck@kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=torvalds@linux-foundation.org \
--cc=unixbhaskar@gmail.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®