All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Wu <josh.wu@atmel.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: <linux-media@vger.kernel.org>, <m.chehab@samsung.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] media: v4l2-image-sizes.h: add SVGA, XGA and UXGA size definitions
Date: Wed, 28 Jan 2015 10:09:22 +0800	[thread overview]
Message-ID: <54C844D2.9040905@atmel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1411272112320.5267@axis700.grange>

Hi, Guennadi

On 11/28/2014 4:13 AM, Guennadi Liakhovetski wrote:
> Hi Josh,
>
> On Thu, 27 Nov 2014, Josh Wu wrote:
>
>> Hi, Guennadi
>>
>> On 11/26/2014 6:23 AM, Guennadi Liakhovetski wrote:
>>> Hi Josh,
>>>
>>> On Tue, 25 Nov 2014, Josh Wu wrote:
>>>
>>>> Add SVGA, UXGA and XGA size definitions to v4l2-image-sizes.h.
>>>> The definitions are sorted by alphabet order.
>>>>
>>>> Signed-off-by: Josh Wu <josh.wu@atmel.com>
>>> Thanks for your patches. I'm ok with these two, but the second of them
>>> depends on the first one, and the first one wouldn't (normally) be going
>>> via the soc-camera tree. Mauro, how would you prefer to handle this?
>>> Should I pick up and push to you both of them or postpone #2 until the
>>> next merge window?
>> The first patch is already merged in the media_tree. If the soc-camera tree
>> will be merged to the media_tree, then there should have no dependency issue.
>> Am I understanding correct?
> Yes, then it should be ok!

Just checking the status of this patch. I don't found this patch in 
media's tree or soc_camera's tree.
Could you take this patch in your tree?

Best Regards,
Josh Wu

>
> Thanks
> Guennadi
>
>> Best Regards,
>> Josh Wu
>>
>>> Thanks
>>> Guennadi
>>>
>>>> ---
>>>>    include/media/v4l2-image-sizes.h | 9 +++++++++
>>>>    1 file changed, 9 insertions(+)
>>>>
>>>> diff --git a/include/media/v4l2-image-sizes.h
>>>> b/include/media/v4l2-image-sizes.h
>>>> index 10daf92..c70c917 100644
>>>> --- a/include/media/v4l2-image-sizes.h
>>>> +++ b/include/media/v4l2-image-sizes.h
>>>> @@ -25,10 +25,19 @@
>>>>    #define QVGA_WIDTH	320
>>>>    #define QVGA_HEIGHT	240
>>>>    +#define SVGA_WIDTH	800
>>>> +#define SVGA_HEIGHT	680
>>>> +
>>>>    #define SXGA_WIDTH	1280
>>>>    #define SXGA_HEIGHT	1024
>>>>      #define VGA_WIDTH	640
>>>>    #define VGA_HEIGHT	480
>>>>    +#define UXGA_WIDTH	1600
>>>> +#define UXGA_HEIGHT	1200
>>>> +
>>>> +#define XGA_WIDTH	1024
>>>> +#define XGA_HEIGHT	768
>>>> +
>>>>    #endif /* _IMAGE_SIZES_H */
>>>> -- 
>>>> 1.9.1
>>>>


  reply	other threads:[~2015-01-28  2:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-25  8:54 [PATCH 1/2] media: v4l2-image-sizes.h: add SVGA, XGA and UXGA size definitions Josh Wu
2014-11-25  8:54 ` [PATCH 2/2] media: ov2640: use the v4l2 " Josh Wu
2014-11-27 21:10   ` Guennadi Liakhovetski
2014-11-25 10:34 ` [PATCH 1/2] media: v4l2-image-sizes.h: add SVGA, XGA and UXGA " Sylwester Nawrocki
2014-11-26  2:06   ` Josh Wu
2014-11-25 22:23 ` Guennadi Liakhovetski
2014-11-27  3:21   ` Josh Wu
2014-11-27 20:13     ` Guennadi Liakhovetski
2015-01-28  2:09       ` Josh Wu [this message]
2015-01-28 20:49         ` Guennadi Liakhovetski

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=54C844D2.9040905@atmel.com \
    --to=josh.wu@atmel.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=m.chehab@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.