From: Dan Carpenter <dan.carpenter@oracle.com>
To: Tony Cho <tony.cho@atmel.com>
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
rachel.kim@atmel.com, chris.park@atmel.com,
austin.shin@atmel.com, linux-wireless@vger.kernel.org,
johnny.kim@atmel.com, Nicolas.FERRE@atmel.com,
adel.noureldin@atmel.com, leo.kim@atmel.com,
adham.abozaeid@atmel.com
Subject: Re: [PATCH 29/32] staging: wilc1000: rename strHostIfRegisterFrame
Date: Wed, 30 Sep 2015 14:00:20 +0300 [thread overview]
Message-ID: <20150930105857.GF7340@mwanda> (raw)
In-Reply-To: <1443606914-25563-7-git-send-email-tony.cho@atmel.com>
On Wed, Sep 30, 2015 at 06:55:11PM +0900, Tony Cho wrote:
> This patch renames strHostIfRegisterFrame to reg_f to avoid CamelCase
> naming convention.
Could we go with "reg_frame"? f is very ambigous.
regards,
dan carpenter
next prev parent reply other threads:[~2015-09-30 11:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 9:55 [PATCH 23/32] staging: wilc1000: rename strHostIfSetMulti Tony Cho
2015-09-30 9:55 ` [PATCH 24/32] staging: wilc1000: rename strHostIfSetOperationMode Tony Cho
2015-09-30 9:55 ` [PATCH 25/32] staging: wilc1000: rename strHostIfSetMacAddress Tony Cho
2015-09-30 9:55 ` [PATCH 26/32] staging: wilc1000: rename strHostIfGetMacAddress Tony Cho
2015-09-30 9:55 ` [PATCH 27/32] staging: wilc1000: rename strHostIfBASessionInfo Tony Cho
2015-09-30 9:55 ` [PATCH 28/32] staging: wilc1000: rename strHostIfRemainOnChan Tony Cho
2015-09-30 9:55 ` [PATCH 29/32] staging: wilc1000: rename strHostIfRegisterFrame Tony Cho
2015-09-30 11:00 ` Dan Carpenter [this message]
2015-09-30 9:55 ` [PATCH 30/32] staging: wilc1000: rename pUserData Tony Cho
2015-09-30 9:55 ` [PATCH 31/32] staging: wilc1000: rename strHostIFDelAllSta Tony Cho
2015-09-30 9:55 ` [PATCH 32/32] staging: wilc1000: fix kernel fail after ifconfig wlan0 up Tony Cho
2015-09-30 10:05 ` Dan Carpenter
2015-09-30 12:21 ` Kim, Leo
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=20150930105857.GF7340@mwanda \
--to=dan.carpenter@oracle.com \
--cc=Nicolas.FERRE@atmel.com \
--cc=adel.noureldin@atmel.com \
--cc=adham.abozaeid@atmel.com \
--cc=austin.shin@atmel.com \
--cc=chris.park@atmel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=johnny.kim@atmel.com \
--cc=leo.kim@atmel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rachel.kim@atmel.com \
--cc=tony.cho@atmel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.