From: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
To: Sachin Kamat <sachin.kamat@linaro.org>
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, m.szyprowski@samsung.com,
k.debski@samsung.com, kmpark@infradead.org, joshi@samsung.com
Subject: Re: [PATCH v5 0/4] Update MFC v4l2 driver to support MFC6.x
Date: Mon, 27 Aug 2012 20:50:01 +0200 [thread overview]
Message-ID: <503BC159.7060106@gmail.com> (raw)
In-Reply-To: <CAK9yfHwit2G3LpDZKx5yZ+zFGBkw3R3Jz+6YHDL-S7aCdnH_xw@mail.gmail.com>
On 08/27/2012 11:31 AM, Sachin Kamat wrote:
> Hi Arun,
>
> The media tree has been re-organized recently.
> It would be useful to re-base your patches against the latest media
> tree (or linux-next).
> MFC driver is now located at "drivers/media/platform/s5p-mfc/"
And you can find some guidelines in this post:
http://www.mail-archive.com/linux-media@vger.kernel.org/msg50498.html
--
Regards,
Sylwester
next prev parent reply other threads:[~2012-08-27 18:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 11:57 [PATCH v5 0/4] Update MFC v4l2 driver to support MFC6.x Arun Kumar K
2012-08-27 9:31 ` Sachin Kamat
2012-08-27 18:50 ` Sylwester Nawrocki [this message]
2012-08-27 11:58 ` [PATCH v5 1/4] [media] s5p-mfc: Update MFCv5 driver for callback based architecture Arun Kumar K
2012-08-28 21:59 ` Kamil Debski
2012-08-27 11:58 ` [PATCH v5 2/4] [media] s5p-mfc: Add MFC variant data to device context Arun Kumar K
2012-08-28 21:59 ` Kamil Debski
2012-08-27 11:58 ` [PATCH v5 3/4] [media] s5p-mfc: MFCv6 register definitions Arun Kumar K
2012-08-27 11:58 ` [PATCH v5 4/4] [media] s5p-mfc: Update MFC v4l2 driver to support MFC6.x Arun Kumar K
-- strict thread matches above, loose matches on Subject: below --
2012-08-28 4:46 [PATCH v5 0/4] " Arun Kumar K
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=503BC159.7060106@gmail.com \
--to=sylvester.nawrocki@gmail.com \
--cc=arun.kk@samsung.com \
--cc=ch.naveen@samsung.com \
--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 \
--cc=sachin.kamat@linaro.org \
/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.