From: Hans Verkuil <hverkuil@xs4all.nl>
To: Junghak Sung <jh1009.sung@samsung.com>,
linux-media@vger.kernel.org, mchehab@osg.samsung.com,
laurent.pinchart@ideasonboard.com, sakari.ailus@iki.fi,
pawel@osciak.com
Cc: inki.dae@samsung.com, sw0312.kim@samsung.com,
nenggun.kim@samsung.com, sangbae90.lee@samsung.com,
rany.kwon@samsung.com
Subject: Re: [RFC PATCH v6 0/4] Refactoring Videobuf2 for common use
Date: Wed, 14 Oct 2015 08:54:32 +0200 [thread overview]
Message-ID: <561DFC28.1030507@xs4all.nl> (raw)
In-Reply-To: <561DA431.9070708@samsung.com>
On 10/14/2015 02:39 AM, Junghak Sung wrote:
>
>
> On 10/13/2015 07:40 PM, Hans Verkuil wrote:
>> On 10/13/15 11:35, Junghak Sung wrote:
>>>
>>>
>>> On 10/12/2015 09:46 PM, Hans Verkuil wrote:
>>>> Hi Junghak,
>>>>
>>>> I've accepted this v6 series and made a pull request for Mauro.
>>>>
>>>
>>> Hi Hans & Mauro,
>>>
>>> First of all, thank you for your acceptance.
>>> But, I have received some build warning reports for this
>>> vb2-refactoring patch from kbuild robot. So, I'd like to fix them
>>> firstly with next patch (v7).
>>
>> If this was a missing const in fimc-lite, then I fixed that myself in
>> your patch. If it was for other things as well, then let me know.
>
> There are two warnings reported from kbuild robot.
> One is related with missing const as you mentioned, and the other is
> format error on dprintk(). (refer to attached email)
> But, I think that format error does not need to be dealt with,
> because it was from original code.
Just make a small patch fixing this on top of v6 and post it as part of the
vb2_thread patch series.
>
>>
>>> Furthermore, I have tried to find out the way to move things related
>>> with vb2_thread to vb2-core. And then.. finally I can come close to
>>> resolve that.
>>> Please, wait for patch v7 if you don't mind.
>>> I will/can send it by this weekend.
>>
>> OK. Please do this vb2_thread work as a patch on top of the existing series.
>> I would like to get what we have today merged asap (with warnings fixed) and
>> this vb2_thread work can always be added later.
>>
>
> OK. If so, I will prepare the next patch(v7) including vb2_thread work
> on v6.
Great!
Thanks,
Hans
prev parent reply other threads:[~2015-10-14 6:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 9:37 [RFC PATCH v6 0/4] Refactoring Videobuf2 for common use Junghak Sung
2015-10-06 9:37 ` [PATCH 1/4] media: videobuf2: Change queue_setup argument Junghak Sung
2015-10-06 9:37 ` [PATCH 2/4] media: videobuf2: Replace v4l2-specific data with vb2 data Junghak Sung
2015-10-06 9:37 ` [PATCH 3/4] media: videobuf2: Prepare to divide videobuf2 Junghak Sung
2015-10-06 9:37 ` [PATCH 4/4] media: videobuf2: Move v4l2-specific stuff to videobuf2-v4l2 Junghak Sung
2015-10-12 12:46 ` [RFC PATCH v6 0/4] Refactoring Videobuf2 for common use Hans Verkuil
2015-10-13 9:35 ` Junghak Sung
2015-10-13 10:40 ` Hans Verkuil
2015-10-14 0:39 ` Junghak Sung
2015-10-14 6:54 ` Hans Verkuil [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=561DFC28.1030507@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=inki.dae@samsung.com \
--cc=jh1009.sung@samsung.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=nenggun.kim@samsung.com \
--cc=pawel@osciak.com \
--cc=rany.kwon@samsung.com \
--cc=sakari.ailus@iki.fi \
--cc=sangbae90.lee@samsung.com \
--cc=sw0312.kim@samsung.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 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.