From: Larry Finger <Larry.Finger@lwfinger.net>
To: Daniel Stamer <daniel@stamer.info>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] rtlwifi: rtl8192se: Fixed coding style issues
Date: Wed, 28 Nov 2012 14:31:14 -0600 [thread overview]
Message-ID: <50B67492.7070404@lwfinger.net> (raw)
In-Reply-To: <1354132879-5154-1-git-send-email-daniel@stamer.info>
On 11/28/2012 02:01 PM, Daniel Stamer wrote:
> This patch fixes coding style issues in the whole rtl8192se driver. All rules
> are used, except for the one which demands empty last lines on block comments.
> Some fields have been altered to create readable lines in 80 columns.
>
> Signed-off-by: Daniel Stamer <daniel@stamer.info>
This patch does not apply against either the wireless-next or wireless-testing
git trees. I could "force" it with wiggle, but John will not, and should not,
need to do that. What source tree did you use?
Larry
next prev parent reply other threads:[~2012-11-28 20:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 20:01 [PATCH] rtlwifi: rtl8192se: Fixed coding style issues Daniel Stamer
2012-11-28 20:31 ` Larry Finger [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-11-28 19:53 Daniel Stamer
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=50B67492.7070404@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=daniel@stamer.info \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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