From: Tomasz Figa <tfiga@chromium.org>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Rajmohan Mani <rajmohan.mani@intel.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
"Toivonen, Tuukka" <tuukka.toivonen@intel.com>
Subject: Re: [PATCH] [media] dw9714: Set the v4l2 focus ctrl step as 1
Date: Thu, 2 Nov 2017 13:06:34 +0900 [thread overview]
Message-ID: <CAAFQd5ASF=ZWNLMhcTLxXQ4j3pauN8Ygh77dGK19LJ=t++q2iw@mail.gmail.com> (raw)
In-Reply-To: <CAAFQd5BWExq1mqAhg6z-=rRvwLh_HMdVdqPx2bGsA4cjjuyDPg@mail.gmail.com>
On Thu, Nov 2, 2017 at 1:00 PM, Tomasz Figa <tfiga@chromium.org> wrote:
> Hi Sakari,
>
> On Thu, Aug 31, 2017 at 6:28 AM, Sakari Ailus <sakari.ailus@iki.fi> wrote:
>> Hi Rajmohan,
>>
>> On Wed, Aug 30, 2017 at 10:48:52AM -0700, Rajmohan Mani wrote:
>>> Current v4l2 focus ctrl step value of 16, limits
>>> the minimum granularity of focus positions to 16.
>>> Setting this value as 1, enables more accurate
>>> focus positions.
>>
>> Thanks for the patch.
>>
>> The recommended limit for line length is 75, not 50 (or 25 or whatever) as
>> it might be in certain Gerrit installations. :-) Please make good use of
>> lines in the future, I've rewrapped the text this time. Thanks.
>
> Has this patch been applied to your tree? I can't find it on
> linux-next or https://git.linuxtv.org/sailus/media_tree.git/ . Just
> want to make sure it doesn't get lost in action.
Okay, my bad. I didn't notice that linux-next is stuck on Oct 18 and
so doesn't include latest media tree.
I confirmed that the patch is indeed present in Mauro's master branch.
Sorry for the noise.
Best regards,
Tomasz
prev parent reply other threads:[~2017-11-02 4:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 17:48 [PATCH] [media] dw9714: Set the v4l2 focus ctrl step as 1 Rajmohan Mani
2017-08-30 21:28 ` Sakari Ailus
2017-08-30 21:39 ` Mani, Rajmohan
2017-11-02 4:00 ` Tomasz Figa
2017-11-02 4:06 ` Tomasz Figa [this message]
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='CAAFQd5ASF=ZWNLMhcTLxXQ4j3pauN8Ygh77dGK19LJ=t++q2iw@mail.gmail.com' \
--to=tfiga@chromium.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rajmohan.mani@intel.com \
--cc=s.nawrocki@samsung.com \
--cc=sakari.ailus@iki.fi \
--cc=tuukka.toivonen@intel.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).