linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sekhar Nori <nsekhar@ti.com>
To: Prabhakar Lad <prabhakar.csengg@gmail.com>
Cc: Russell King <rmk+kernel@arm.linux.org.uk>,
	<davinci-linux-open-source@linux.davincidsp.com>,
	Mauro Carvalho Chehab <mchehab@redhat.com>,
	<linux-media@vger.kernel.org>
Subject: Re: [PATCH] media: davinci: kconfig: fix incorrect selects
Date: Tue, 12 Mar 2013 13:46:30 +0530	[thread overview]
Message-ID: <513EE45E.6050004@ti.com> (raw)
In-Reply-To: <CA+V-a8vaNzio4RYqq8xwe=bOS0F+2t_mkwDWcQ99GbChC97Ayg@mail.gmail.com>

On 3/12/2013 10:44 AM, Prabhakar Lad wrote:
> Hi Sekhar,
> 
> Thanks for the patch! few nits below
> 
> also version number for patch is missing as this should have been v2 :)

Missed that, sorry.

> BTW this patch still is not  present in media list.

Not sure what is happening there. Its an open list as far as I can see
and there is no message I am getting back from list. Most probably vger
thinks I am spamming, but I am not sure why.

>>
>>  config VIDEO_DAVINCI_VPBE_DISPLAY
>>         tristate "DM644X/DM365/DM355 VPBE HW module"
> why not change this to 'TI DaVinci VPBE Video Display' as done for vpif ?

Okay, will do. I would like to remind that I have not tested this patch
(not loaded the modules and connected a video device). If you can get
some testing done on this it will be great.

Thanks,
Sekhar

  parent reply	other threads:[~2013-03-12  8:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1362492801-13202-1-git-send-email-nsekhar@ti.com>
2013-03-06  9:29 ` [PATCH] media: davinci: kconfig: fix incorrect selects Prabhakar Lad
2013-03-06 10:07   ` Sekhar Nori
2013-03-06 10:16     ` Prabhakar Lad
2013-03-06 10:21       ` Prabhakar Lad
2013-03-06 10:23       ` Sekhar Nori
2013-03-06 10:35         ` Prabhakar Lad
2013-03-06 14:21           ` Sekhar Nori
2013-03-07  7:17             ` Prabhakar Lad
2013-03-07 11:24               ` Sekhar Nori
2013-03-07 11:39                 ` Prabhakar Lad
     [not found]                   ` <1363004536-27314-1-git-send-email-nsekhar@ti.com>
2013-03-12  5:14                     ` Prabhakar Lad
2013-03-12  6:48                       ` cstsai
2013-03-12  8:16                       ` Sekhar Nori [this message]
     [not found]                         ` <1363079692-16683-1-git-send-email-nsekhar@ti.com>
2013-03-16  8:36                           ` [PATCH v3] " Prabhakar Lad
2013-03-18  8:42                             ` Sekhar Nori
2013-04-08  8:09                           ` Prabhakar Lad
2013-04-08  9:53                             ` Sekhar Nori
2013-05-13  9:41                           ` [v3] " Paul Bolle
2013-05-13  9:57                             ` Prabhakar Lad
2013-05-13 10:05                               ` Paul Bolle
2013-05-13 10:41                                 ` Prabhakar Lad
2013-05-23 10:23                                   ` Hans Verkuil
2013-05-23 10:25                                     ` Prabhakar Lad
2013-03-19 10:39                         ` [PATCH] " 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=513EE45E.6050004@ti.com \
    --to=nsekhar@ti.com \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.com \
    --cc=prabhakar.csengg@gmail.com \
    --cc=rmk+kernel@arm.linux.org.uk \
    /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).