From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Dror Cohen <dror@liveu.tv>
Cc: linux-media@vger.kernel.org,
davinci-linux-open-source@linux.davincidsp.com,
mchehab@infradead.org
Subject: Re: [PATCH 0/1] media/video: vpif: fixing function name start to vpif_config_params
Date: Thu, 02 Aug 2012 14:51:28 +0400 [thread overview]
Message-ID: <501A5BB0.4090809@mvista.com> (raw)
In-Reply-To: <1343893232-19543-1-git-send-email-dror@liveu.tv>
Hello.
On 02-08-2012 11:40, Dror Cohen wrote:
> This patch address the issue that a function named config_vpif_params should
> be vpif_config_params. This, however, conflicts with two structures defined
> already.
Function names shouldn't conflict with the structure tags. Structure tags
always follow 'struct' keyword and are only valid in this context.
> So I changed the structures to config_vpif_params_t (origin was
> vpif_config_params)
WBR, Sergei
prev parent reply other threads:[~2012-08-02 10:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 7:40 [PATCH 0/1] media/video: vpif: fixing function name start to vpif_config_params Dror Cohen
2012-08-02 7:40 ` [PATCH 1/1] " Dror Cohen
2012-08-02 10:49 ` Sergei Shtylyov
2012-08-02 10:51 ` Sergei Shtylyov [this message]
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=501A5BB0.4090809@mvista.com \
--to=sshtylyov@mvista.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).