From: Manjunath Hadli <manjunath.hadli@ti.com>
To: Dror Cohen <dror@liveu.tv>, <mchehab@infradead.org>
Cc: <linux-media@vger.kernel.org>,
<davinci-linux-open-source@linux.davincidsp.com>,
Manjunath Hadli <manjunath.hadli@ti.com>
Subject: Re: [PATCH 0/1 v2] media/video: vpif: fixing function name start to vpif_config_params
Date: Mon, 13 Aug 2012 19:43:29 +0530 [thread overview]
Message-ID: <50290B89.7070100@ti.com> (raw)
In-Reply-To: <1344494017-18099-1-git-send-email-dror@liveu.tv>
Hi Dror,
Thanks for the patch.
Mauro,
I'll queue this patch for v3.7 through my tree.
On Thursday 09 August 2012 12:03 PM, Dror Cohen wrote:
> This patch address the issue that a function named config_vpif_params should
> be vpif_config_params. However this name is shared with two structures defined
> already. So I changed the structures to config_vpif_params (origin was
> vpif_config_params)
>
> v2 changes: softer wording in description and the structs are now
> defined without _t
>
> Dror Cohen (1):
> fixing function name start to vpif_config_params
>
> drivers/media/video/davinci/vpif.c | 6 +++---
> drivers/media/video/davinci/vpif_capture.c | 2 +-
> drivers/media/video/davinci/vpif_capture.h | 2 +-
> drivers/media/video/davinci/vpif_display.c | 2 +-
> drivers/media/video/davinci/vpif_display.h | 2 +-
> 5 files changed, 7 insertions(+), 7 deletions(-)
Acked-by: Manjunath Hadli <manjunath.hadli@ti.com>
Thx,
--Manju
next prev parent reply other threads:[~2012-08-13 14:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 6:33 [PATCH 0/1 v2] media/video: vpif: fixing function name start to vpif_config_params Dror Cohen
2012-08-09 6:33 ` [PATCH 1/1 " Dror Cohen
2012-08-13 14:13 ` Manjunath Hadli [this message]
2012-09-26 20:20 ` [PATCH 0/1 " Mauro Carvalho Chehab
2012-09-27 5:16 ` Prabhakar Lad
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=50290B89.7070100@ti.com \
--to=manjunath.hadli@ti.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=dror@liveu.tv \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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).