From: Andy Walls <awalls@md.metrocast.net>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
Nayden Kanchev <nkanchev@mm-sol.com>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
David Cohen <dacohen@gmail.com>,
Kim HeungJun <riverful@gmail.com>,
andrew.b.adams@gmail.com, Sung Hee Park <shpark7@stanford.edu>
Subject: Re: [RFC v4] V4L2 API for flash devices
Date: Sat, 14 May 2011 09:13:00 -0400 [thread overview]
Message-ID: <1305378780.2434.18.camel@localhost> (raw)
In-Reply-To: <201105071446.56843.hverkuil@xs4all.nl>
On Sat, 2011-05-07 at 14:46 +0200, Hans Verkuil wrote:
> On Thursday, May 05, 2011 20:49:21 Sakari Ailus wrote:
> >
> >
> > enum v4l2_flash_strobe_whence {
> > V4L2_FLASH_STROBE_WHENCE_SOFTWARE,
> > V4L2_FLASH_STROBE_WHENCE_EXTERNAL,
> > };
>
> Perhaps use 'type' instead of 'whence'? English isn't my native language,
> but it sounds pretty archaic to me.
"SOURCE" is better than "WHENCE" here.
"whence" is certainly very formal and used very little. "whence" likely
still gets some use in English, simply because a terse synonym doesn't
exist.
The problem with using whence is that many English speakers won't know
its correct definition.
"whence" means "from what source, origin, or place"
In your use here, the implicit "from" in the definition of whence is
essential. However, most (American) English speakers that I know think
"whence" simply means "where".
Regards,
Andy
next prev parent reply other threads:[~2011-05-14 12:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 18:49 [RFC v4] V4L2 API for flash devices Sakari Ailus
2011-05-07 12:46 ` Hans Verkuil
2011-05-07 17:42 ` Sylwester Nawrocki
2011-05-08 22:11 ` Sakari Ailus
2011-05-10 20:40 ` Sylwester Nawrocki
2011-05-17 20:34 ` Sakari Ailus
2011-05-18 7:10 ` Laurent Pinchart
2011-05-18 7:30 ` Sakari Ailus
2011-05-18 22:21 ` Sylwester Nawrocki
2011-05-19 8:12 ` Sakari Ailus
2011-06-07 12:17 ` Mauro Carvalho Chehab
2011-05-08 15:48 ` Sakari Ailus
2011-05-14 13:13 ` Andy Walls [this message]
2011-05-16 9:23 ` Sakari Ailus
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=1305378780.2434.18.camel@localhost \
--to=awalls@md.metrocast.net \
--cc=andrew.b.adams@gmail.com \
--cc=dacohen@gmail.com \
--cc=g.liakhovetski@gmx.de \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=nkanchev@mm-sol.com \
--cc=riverful@gmail.com \
--cc=sakari.ailus@maxwell.research.nokia.com \
--cc=shpark7@stanford.edu \
/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.