All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Kamil Debski <k.debski@samsung.com>
Cc: 'Arun Kumar K' <arun.kk@samsung.com>,
	linux-media@vger.kernel.org, jtp.park@samsung.com,
	janghyuck.kim@samsung.com, jaeryul.oh@samsung.com,
	ch.naveen@samsung.com,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	hverkuil@xs4all.nl, kmpark@infradead.org, joshi@samsung.com
Subject: Re: [PATCH v9 0/6] Update MFC v4l2 driver to support MFC6.x
Date: Tue, 02 Oct 2012 19:10:36 +0200	[thread overview]
Message-ID: <506B200C.5090600@samsung.com> (raw)
In-Reply-To: <01b901cda08f$5e382e00$1aa88a00$%debski@samsung.com>

Hello,

On 10/02/2012 01:16 PM, Kamil Debski wrote:
> Hi Arun,
> 
> Thank you for your hard work with these patches.
> I think that they are ready to be merged.

I've just picked up these patches and have sent the pull request.

Thanks,
Sylwester


  reply	other threads:[~2012-10-02 17:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-02 14:55 [PATCH v9 0/6] Update MFC v4l2 driver to support MFC6.x Arun Kumar K
2012-10-02 11:16 ` Kamil Debski
2012-10-02 17:10   ` Sylwester Nawrocki [this message]
2012-10-02 14:55 ` [PATCH v9 1/6] [media] v4l: Add fourcc definitions for new formats Arun Kumar K
2012-10-02 11:16   ` Kamil Debski
2012-10-02 14:55 ` [PATCH v9 2/6] [media] v4l: Add control definitions for new H264 encoder features Arun Kumar K
2012-10-02 11:16   ` Kamil Debski
2012-10-02 14:55 ` [PATCH v9 3/6] [media] s5p-mfc: Update MFCv5 driver for callback based architecture Arun Kumar K
2012-10-02 11:16   ` Kamil Debski
2012-10-02 14:55 ` [PATCH v9 4/6] [media] s5p-mfc: Add MFC variant data to device context Arun Kumar K
2012-10-02 11:16   ` Kamil Debski
2012-10-02 14:55 ` [PATCH v9 5/6] [media] s5p-mfc: MFCv6 register definitions Arun Kumar K
2012-10-02 11:16   ` Kamil Debski
2012-10-02 14:55 ` [PATCH v9 6/6] [media] s5p-mfc: Update MFC v4l2 driver to support MFC6.x Arun Kumar K
2012-10-02 11:16   ` Kamil Debski

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=506B200C.5090600@samsung.com \
    --to=s.nawrocki@samsung.com \
    --cc=arun.kk@samsung.com \
    --cc=ch.naveen@samsung.com \
    --cc=hverkuil@xs4all.nl \
    --cc=jaeryul.oh@samsung.com \
    --cc=janghyuck.kim@samsung.com \
    --cc=joshi@samsung.com \
    --cc=jtp.park@samsung.com \
    --cc=k.debski@samsung.com \
    --cc=kmpark@infradead.org \
    --cc=linux-media@vger.kernel.org \
    --cc=m.szyprowski@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.