All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Larry Finger <Larry.Finger@lwfinger.net>, kvalo@codeaurora.org
Cc: linux-wireless@vger.kernel.org,
	Yan-Hsuan Chuang <yhchuang@realtek.com>,
	Pkshih <pkshih@realtek.com>, Birming Chiu <birming@realtek.com>,
	Shaofu <shaofu@realtek.com>, Steven Ting <steventing@realtek.com>
Subject: Re: [PATCH 12/13] rtlwifi: btcoex: 21a 1ant: fix some coding style issues
Date: Mon, 17 Apr 2017 10:28:26 -0700	[thread overview]
Message-ID: <1492450106.8661.11.camel@perches.com> (raw)
In-Reply-To: <869a1d9b-79dc-9d5a-c4f3-efb99c1b1ff7@lwfinger.net>

On Mon, 2017-04-17 at 12:13 -0500, Larry Finger wrote:
> On 04/17/2017 11:09 AM, Joe Perches wrote:
> > On Sun, 2017-04-16 at 19:06 -0500, Larry Finger wrote:
> > > From: Yan-Hsuan Chuang <yhchuang@realtek.com>
> > > 
> > > Fix alignment for coding style consistency.
> > 
> > aside:
> > 
> > Are all the btcoexist variants for this code identical?
> > 
> > 8192e2ant.c 8723b1ant.c 8723b2ant.c 8821a1ant.c 8821a2ant.c
> > 
> > Maybe some of these functions should be centralized.
> 
> They are not identical, but some of the functions could certainly be centralized.

I was writing specifically about functions not modules.

> The problem is that the btcoex software at Realtek is multi platform, and 
> written by a group that has not been too eager to implement this kind of 
> suggestion. If we were to force the issue, then the maintenance load on the 
> separate Linux group at Realtek would be greatly increased. This current set of 
> updates has already been delayed for at least two years while they found the 
> resources to be able to adhere to the "small change" policy of Linux. For that 
> reason alone, I would not be in favor of forcing the issue.

No worries, it just looked pretty mindless to copy/paste
relatively large blocks of code and then do trivial
whitespace fixes to them individually and separately.

  reply	other threads:[~2017-04-17 17:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-17  0:06 [PATCH 00/13] rtlwifi: btcoex: Second set of 21a 1ant changes Larry Finger
2017-04-17  0:06 ` [PATCH 01/13] rtlwifi: btcoex: 21a 1ant: set tdma and coex table when wifi is idle Larry Finger
2017-04-21  6:38   ` [01/13] " Kalle Valo
2017-04-17  0:06 ` [PATCH 02/13] rtlwifi: btcoex: 21a 1ant: more bt profiling when wifi receives special packet Larry Finger
2017-04-17  0:06 ` [PATCH 03/13] rtlwifi: btcoex: 21a 1ant: shorten wifi slot when connected scan Larry Finger
2017-04-17  0:06 ` [PATCH 04/13] rtlwifi: btcoex: 21a 1ant: react to special packet when wifi is not scanning Larry Finger
2017-04-17  0:06 ` [PATCH 05/13] rtlwifi: btcoex: 21a 1ant: coex table and tdma settings for softap mode Larry Finger
2017-04-17  0:06 ` [PATCH 06/13] rtlwifi: btcoex: 21a 1ant: wifi slot time adjustment Larry Finger
2017-04-17  0:06 ` [PATCH 07/13] rtlwifi: btcoex: 21a 1ant: normal mode for retry limit when connected Larry Finger
2017-04-17  0:06 ` [PATCH 08/13] rtlwifi: btcoex: 21a 1ant: mark packet high priority when scanning Larry Finger
2017-04-17  0:06 ` [PATCH 09/13] rtlwifi: btcoex: 21a 1ant: use default value when initiating coex Larry Finger
2017-04-17  0:06 ` [PATCH 10/13] rtlwifi: btcoex: 21a 1ant: re-init coex after wifi leaves IPS Larry Finger
2017-04-17  0:06 ` [PATCH 11/13] rtlwifi: btcoex: 21a 1ant: treat ARP as special packet Larry Finger
2017-04-17  0:06 ` [PATCH 12/13] rtlwifi: btcoex: 21a 1ant: fix some coding style issues Larry Finger
2017-04-17 16:09   ` Joe Perches
2017-04-17 17:13     ` Larry Finger
2017-04-17 17:28       ` Joe Perches [this message]
2017-04-17  0:07 ` [PATCH 13/13] rtlwifi: btcoex: 21a 1ant: add bt_tx_rx_mask into bt info Larry Finger

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=1492450106.8661.11.camel@perches.com \
    --to=joe@perches.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=birming@realtek.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.com \
    --cc=shaofu@realtek.com \
    --cc=steventing@realtek.com \
    --cc=yhchuang@realtek.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.