From: mchehab@redhat.com (Mauro Carvalho Chehab)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 0/2] ARM: davinci: dm355: add support for vpbe display
Date: Mon, 8 Apr 2013 07:56:06 -0300 [thread overview]
Message-ID: <20130408075606.5a59d32c@redhat.com> (raw)
In-Reply-To: <51629DA8.3040806@ti.com>
Hi Sekhar,
Em Mon, 8 Apr 2013 16:06:24 +0530
Sekhar Nori <nsekhar@ti.com> escreveu:
> On 4/8/2013 2:56 PM, Prabhakar lad wrote:
> > From: Lad, Prabhakar <prabhakar.csengg@gmail.com>
> >
> > This patch series enables VPBE display driver on DM355.
>
> These (this and the DM365 one) patches look good to me. I need to get an
> immutable branch from Mauro where dependencies are queued and then I can
> generate a pull request for these for ARM SoC.
Are you mean a branch at the media development tree for you to sent
pull requests for me? If so, just use the "master" branch at the media
tree:
http://git.linuxtv.org/media_tree.git
The master branch there is never rebased. I'll likely start to have
topic branches on the next Kernel cycle, also at the same tree.
Regards,
Mauro
next prev parent reply other threads:[~2013-04-08 10:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 9:26 [PATCH v8 0/2] ARM: davinci: dm355: add support for vpbe display Prabhakar lad
2013-04-08 9:26 ` [PATCH v8 1/2] ARM: davinci: dm355: add support for v4l2 video display Prabhakar lad
2013-04-12 8:28 ` Sekhar Nori
2013-04-08 9:26 ` [PATCH v8 2/2] ARM: davinci: dm355 EVM: add support for VPBE display Prabhakar lad
2013-04-08 10:36 ` [PATCH v8 0/2] ARM: davinci: dm355: add support for vpbe display Sekhar Nori
2013-04-08 10:56 ` Mauro Carvalho Chehab [this message]
2013-04-08 11:47 ` Sekhar Nori
2013-04-08 12:56 ` Mauro Carvalho Chehab
2013-04-09 11:18 ` Sekhar Nori
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=20130408075606.5a59d32c@redhat.com \
--to=mchehab@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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).