From: Sylwester Nawrocki <snjw23@gmail.com>
To: javier Martin <javier.martin@vista-silicon.com>
Cc: linux-media@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, m.szyprowski@samsung.com,
laurent.pinchart@ideasonboard.com, s.nawrocki@samsung.com,
hverkuil@xs4all.nl, kyungmin.park@samsung.com,
shawn.guo@linaro.org, richard.zhao@linaro.org,
fabio.estevam@freescale.com, kernel@pengutronix.de,
s.hauer@pengutronix.de, r.schwebel@pengutronix.de
Subject: Re: [PATCH v4 0/2] Add support form eMMa-PrP in i.MX2 chips as a mem2mem device.
Date: Mon, 02 Jan 2012 22:12:46 +0100 [thread overview]
Message-ID: <4F021DCE.8000105@gmail.com> (raw)
In-Reply-To: <CACKLOr1RujFbuTnF=DkCTB=paVUq7=j1Ru_RU7DWyuJedM+Cvg@mail.gmail.com>
Hi Javier,
On 01/02/2012 10:31 AM, javier Martin wrote:
> Hi,
> do you have any more concerns or comments on this patch?
> I can't find it in media_tree. Has it been merged somewhere else?
If you think your driver is good enough for merging, if you didn't
do so already, you should normally send Mauro a git pull request.
Please see:
http://linuxtv.org/wiki/index.php/Maintaining_Git_trees#how_to_submit_a_-git_pull_request
And here you can find some examples:
http://patchwork.linuxtv.org/project/linux-media/list/?state=*&q=PULL&archive=both
--
Regards,
Sylwester
next prev parent reply other threads:[~2012-01-02 21:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 11:43 [PATCH v4 0/2] Add support form eMMa-PrP in i.MX2 chips as a mem2mem device Javier Martin
2011-12-12 11:43 ` [PATCH v4 1/2] MEM2MEM: Add support for eMMa-PrP mem2mem operations Javier Martin
2011-12-12 11:43 ` [PATCH v4 2/2] MX2: Add platform definitions for eMMa-PrP device Javier Martin
2012-01-02 9:31 ` [PATCH v4 0/2] Add support form eMMa-PrP in i.MX2 chips as a mem2mem device javier Martin
2012-01-02 21:12 ` Sylwester Nawrocki [this message]
2012-01-03 7:43 ` javier Martin
2012-01-03 8:56 ` javier Martin
2012-01-03 9:53 ` Sylwester Nawrocki
2012-02-28 10:28 ` Mauro Carvalho Chehab
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=4F021DCE.8000105@gmail.com \
--to=snjw23@gmail.com \
--cc=fabio.estevam@freescale.com \
--cc=hverkuil@xs4all.nl \
--cc=javier.martin@vista-silicon.com \
--cc=kernel@pengutronix.de \
--cc=kyungmin.park@samsung.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=r.schwebel@pengutronix.de \
--cc=richard.zhao@linaro.org \
--cc=s.hauer@pengutronix.de \
--cc=s.nawrocki@samsung.com \
--cc=shawn.guo@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 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).