From: Greg KH <gregkh@suse.de>
To: Andy Walls <awalls@md.metrocast.net>
Cc: alsa-devel@alsa-project.org,
sakari.ailus@maxwell.research.nokia.com,
broonie@opensource.wolfsonmicro.com, clemens@ladisch.de,
linux-kernel@vger.kernel.org, Hans Verkuil <hverkuil@xs4all.nl>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-media@vger.kernel.org
Subject: Re: [RFC/PATCH v7 01/12] media: Media device node support
Date: Thu, 6 Jan 2011 16:31:40 -0800 [thread overview]
Message-ID: <20110107003140.GA3828@suse.de> (raw)
In-Reply-To: <0iuif2gxlcatpj50djfn40p8.1294359457034@email.android.com>
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Thu, Jan 06, 2011 at 07:24:27PM -0500, Andy Walls wrote:
> Why, yes, there is a standard:
>
> http://pubs.opengroup.org/onlinepubs/009695399/functions/xsh_chap02_03.html
>
> A somewhat verbose description of the errnos is in section 2.3.
Ah, so perhaps -ENXIO is the correct thing to return with here.
thanks,
greg k-h
next prev parent reply other threads:[~2011-01-07 0:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 0:24 [RFC/PATCH v7 01/12] media: Media device node support Andy Walls
2011-01-07 0:31 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-01-07 1:04 Andy Walls
2010-12-20 11:36 [RFC/PATCH v7 00/12] Media controller (core and V4L2) Laurent Pinchart
2010-12-20 11:36 ` [RFC/PATCH v7 01/12] media: Media device node support Laurent Pinchart
2010-12-23 3:32 ` Greg KH
2010-12-24 11:59 ` Laurent Pinchart
2011-01-06 22:19 ` Greg KH
2011-01-06 23:27 ` Hans Verkuil
2011-01-06 23:46 ` Greg KH
2011-01-10 14:09 ` Laurent Pinchart
2011-01-11 0:15 ` Raymond Yau
2010-12-23 3:34 ` Greg KH
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=20110107003140.GA3828@suse.de \
--to=gregkh@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=awalls@md.metrocast.net \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=clemens@ladisch.de \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@maxwell.research.nokia.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;
as well as URLs for NNTP newsgroup(s).