linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Omar Ramirez Luna <omar.ramirez@ti.com>
To: "Sapiens, Rene" <rene.sapiens@ti.com>
Cc: "greg@kroah.com" <greg@kroah.com>,
	"gregkh@suse.de" <gregkh@suse.de>,
	"ohad@wizery.com" <ohad@wizery.com>,
	"ameya.palande@nokia.com" <ameya.palande@nokia.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 00/15] ti dspbridge: Remove CamelCase, reagroup variables
Date: Fri, 16 Jul 2010 19:17:12 -0500	[thread overview]
Message-ID: <4C40F688.80507@ti.com> (raw)
In-Reply-To: <1278728649-21012-1-git-send-email-rene.sapiens@ti.com>

On 7/9/2010 9:23 PM, Sapiens, Rene wrote:
> The intention of this serie of patches is to rename the remaining variables
> with camel case. Words will be renamed avoiding CamelCase and Hungarian
> notation. Also the variables in the prototypes  will be renamed to make them
> match with the ones in the function definitions.
>
[...]
>   74 files changed, 2471 insertions(+), 2439 deletions(-)
>
>

Some of your patches produce:

warning: drivers/staging/tidspbridge/include/dspbridge/dspdefs.h has 
type 100644, expected 100755

None of the files had their permissions changed so I guess they should 
be fine to merge, unless anybody else complains... so ACK.

For future patches please check you are not changing file mode or use:

git config core.filemode false

Regards,

Omar

  parent reply	other threads:[~2010-07-17  0:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-10  2:23 [PATCH 00/15] ti dspbridge: Remove CamelCase, reagroup variables Rene Sapiens
2010-07-10  2:23 ` [PATCH 01/15] staging:ti dspbridge: Rename words with camel case Rene Sapiens
2010-07-10  2:23   ` [PATCH 02/15] " Rene Sapiens
2010-07-10  2:23     ` [PATCH 03/15] " Rene Sapiens
2010-07-10  2:23       ` [PATCH 04/15] " Rene Sapiens
2010-07-10  2:23         ` [PATCH 05/15] " Rene Sapiens
2010-07-10  2:24           ` [PATCH 06/15] " Rene Sapiens
2010-07-10  2:24             ` [PATCH 07/15] " Rene Sapiens
2010-07-10  2:24               ` [PATCH 08/15] " Rene Sapiens
2010-07-10  2:24                 ` [PATCH 09/15] " Rene Sapiens
2010-07-10  2:24                   ` [PATCH 10/15] " Rene Sapiens
2010-07-10  2:24                     ` [PATCH 11/15] " Rene Sapiens
2010-07-10  2:24                       ` [PATCH 12/15] " Rene Sapiens
2010-07-10  2:24                         ` [PATCH 13/15] " Rene Sapiens
2010-07-10  2:24                           ` [PATCH 14/15] " Rene Sapiens
2010-07-10  2:24                             ` [PATCH 15/15] staging:ti dspbridge: make variables in prototypes match within functions definitions Rene Sapiens
2010-07-17  0:17 ` Omar Ramirez Luna [this message]
2010-07-22 17:43   ` [PATCH 00/15] ti dspbridge: Remove CamelCase, reagroup variables Greg KH
2010-07-22 17:46 ` Greg KH

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=4C40F688.80507@ti.com \
    --to=omar.ramirez@ti.com \
    --cc=ameya.palande@nokia.com \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=ohad@wizery.com \
    --cc=rene.sapiens@ti.com \
    /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).