From: "M. Vefa Bicakci" <m.v.b@runbox.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
Jes.Sorensen@redhat.com, joe@perches.com,
Larry.Finger@lwfinger.net, mail@beyermatthias.de
Subject: Re: [PATCH v3 01/15] staging: rtl8723au: Reformat whitespace to increase readability
Date: Sat, 28 Mar 2015 08:39:49 -0400 [thread overview]
Message-ID: <5516A115.4040208@runbox.com> (raw)
In-Reply-To: <20150326121810.GA15960@kroah.com>
On 26/03/15 08:18 AM, Greg KH wrote:
> On Thu, Mar 19, 2015 at 12:39:04AM -0400, M. Vefa Bicakci wrote:
>> Adjust the whitespace in the signature, local variable declaration and
>> initialization parts of a number of functions to increase readability
>> in rtl8723au's rtw_security.c.
>>
>> v2: Make sure that the arcfour_encrypt function's argument list is split
>> according to the kernel code style.
>
> The "v2" stuff here should go below the --- line, otherwise it will show
> up in the changelog :(
>
> Please fix these all up and resend.
Hello Greg,
Thank you for the review!
I have addressed your comment in my local repository and I hope to send the 4th
revision of the patches soon.
Thanks again,
Vefa
next prev parent reply other threads:[~2015-03-28 12:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 4:39 [PATCH v3 00/15] checkpatch clean-up of rtl8723au's rtw_security.c M. Vefa Bicakci
2015-03-19 4:39 ` [PATCH v3 01/15] staging: rtl8723au: Reformat whitespace to increase readability M. Vefa Bicakci
2015-03-26 12:18 ` Greg KH
2015-03-28 12:39 ` M. Vefa Bicakci [this message]
2015-03-19 4:39 ` [PATCH v3 02/15] staging: rtl8723au: Fix "before/around/after" whitespace issues M. Vefa Bicakci
2015-03-19 4:39 ` [PATCH v3 03/15] staging: rtl8723au: else should follow close brace M. Vefa Bicakci
2015-03-19 4:39 ` [PATCH v3 04/15] staging: rtl8723au: Fix the indentation of two lines M. Vefa Bicakci
2015-03-19 4:39 ` [PATCH v3 05/15] staging: rtl8723au: Reorganize a few functions to remove indentation M. Vefa Bicakci
2015-03-19 4:39 ` [PATCH v3 06/15] staging: rtl8723au: else is not generally useful after a return M. Vefa Bicakci
2015-03-19 4:39 ` [PATCH v3 07/15] staging: rtl8723au: Remove unneeded curly braces M. Vefa Bicakci
2015-03-19 4:39 ` [PATCH v3 08/15] staging: rtl8723au: trailing statements should be on next line M. Vefa Bicakci
2015-03-19 4:39 ` [PATCH v3 09/15] staging: rtl8723au: that open brace should be on the previous line M. Vefa Bicakci
2015-03-19 4:39 ` [PATCH v3 10/15] staging: rtl8723au: No spaces at the start of a line M. Vefa Bicakci
2015-03-19 4:39 ` [PATCH v3 11/15] staging: rtl8723au: Adjust whitespace in and around comments M. Vefa Bicakci
2015-03-19 4:39 ` [PATCH v3 12/15] staging: rtl8723au: suspect code indent for conditional statements M. Vefa Bicakci
2015-03-19 4:39 ` [PATCH v3 13/15] staging: rtl8723au: Rework two byte array comparisons M. Vefa Bicakci
2015-03-19 4:39 ` [PATCH v3 14/15] staging: rtl8723au: Use __func__ in trace logs M. Vefa Bicakci
2015-03-19 4:39 ` [PATCH v3 15/15] staging: rtl8723au: Remove unneeded comments M. Vefa Bicakci
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=5516A115.4040208@runbox.com \
--to=m.v.b@runbox.com \
--cc=Jes.Sorensen@redhat.com \
--cc=Larry.Finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mail@beyermatthias.de \
/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).