linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Ketrenos <jketreno@linux.intel.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH]  Add iwlwifi wireless drivers
Date: Wed, 16 May 2007 21:28:04 -0700	[thread overview]
Message-ID: <464BD9D4.4020909@linux.intel.com> (raw)
In-Reply-To: <20070516182700.912a21ed.randy.dunlap@oracle.com>

Randy Dunlap wrote:
> On Wed, 16 May 2007 14:45:32 -0700 James Ketrenos wrote:
> 
>> This patch adds the iwlwifi project directory and sources needed to 
>> build the mac80211 based wireless drivers for the Intel PRO/Wireless 
>> 3945ABG/BG Network Connection and Intel Wireless WiFi Link AGN adapters.
>>
>> Signed-off-by: James Ketrenos <jketreno@linux.intel.com>
>> ---
>>
>> NOTE:  The patch is 597k and can be found at:
>>
>> 	http://intellinuxwireless.org/iwlwifi/0001-Add-iwlwifi-wireless-drivers.patch
>>
>> Patch is against wireless-dev commit-id be8662897~
> 
> 
> Some comments/review, mostly not-code-related:
...
> 3.  Indent labels: with 0 or 1 space, not with 7 spaces.
> Using 7 spaces hides them, makes them too difficult to see/find.

I can correct this with:

	sed -i -e 's,^\(.*\)default:,foo\1default:,g' \
		-e 's,^[[:space:]]*\([[:alpha:]]\+[[:alnum:]]*:\)$, \1,g' \
		-e 's,^foo\(.*\)default:,\1default:,g' origin/*.[ch]

However scripts/Lindent undoes it.  Is there a way to keep Lindent from indenting labels?  When I looked at indent's man page it only talked about case labels.

...
> 12.  36 lines end with trailing whitespace.   :( 

I must have forgotten to run Lindent on the final code.  I'll run it (or just a sed to remove the trailing whitespace) on the code before I submit the version that addresses all the comments.

...
> 15.  Limit source lines to <= 80 columns (this patch contains
> over 200 lines that are > 80 columns).
> 

Confirmed 239 instances of > 80 columns by:

	for i in *.[ch]; do 
		echo $i
		sed -e 's,\t,        ,g' $i | 
			grep -n '^.\{80\}.\+$'
	done

I thought Lindent would handle that prettily, but I guess not.  

It seems to have enforced 80-column on some lines (sticking a bunch of right justified parameters) and on others it has made things a lot worse.   

Lindent seems to have converted space-justified column alignment into tab-justified column alignment, which frequently doesn't fit in 80 columns.  For example:

          1         2         3         4         5         6         7
01234567890123456789012345678901234567890123456789012345678901234567890123456789
int param_antenna = 0;<-10spc->/* def: 0 = both antennas (use diversity) */

was changed to:

         1         2         3         4         5         6         7
01234567890123456789012345678901234567890123456789012345678901234567890123456789
int param_antenna = 0;<-  two tabs  ->/* def: 0 = both antennas (use diversity) */

Is there another tool people use besides Lindent to enforce style?
 
Thanks,
James

  reply	other threads:[~2007-05-17  5:39 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-16 21:45 [PATCH] Add iwlwifi wireless drivers James Ketrenos
2007-05-17  1:27 ` Randy Dunlap
2007-05-17  4:28   ` James Ketrenos [this message]
2007-05-17  5:57     ` Jeff Garzik
2007-05-22 21:38       ` James Ketrenos
2007-05-18 19:01   ` James Ketrenos
2007-05-18 20:57     ` Jeff Garzik
2007-05-18 20:54       ` James Ketrenos
2007-05-18 21:06     ` Randy Dunlap
2007-05-22 18:39       ` John W. Linville
2007-05-22 18:29         ` James Ketrenos
2007-05-17  1:51 ` Michael Wu
2007-05-17  2:56   ` Jeff Garzik
2007-05-17  3:55     ` Michael Wu
2007-05-17  8:52   ` Christoph Hellwig
2007-05-22 19:16   ` James Ketrenos
2007-05-22 23:00     ` Jeff Garzik
2007-05-22 21:49       ` James Ketrenos
2007-05-22 23:41         ` Jeff Garzik
2007-05-22 22:56           ` James Ketrenos
2007-05-23  0:58             ` Jeff Garzik
2007-05-23 18:17               ` James Ketrenos
2007-05-23 19:59                 ` Jeff Garzik
2007-05-23 19:30                   ` James Ketrenos
2007-05-23  1:06     ` Michael Wu
2007-05-23  1:46       ` Jeff Garzik
2007-05-17  3:35 ` [PATCH] Add iwlwifi wireless drivers [part 2/2] Randy Dunlap
2007-05-17 15:03   ` Stephen Hemminger
2007-05-17 15:05   ` Stephen Hemminger
2007-05-18  7:04     ` Johannes Berg
2007-05-18 20:33   ` James Ketrenos
2007-05-18 22:05     ` Jeff Garzik
2007-05-18 21:31       ` James Ketrenos
2007-05-18 22:50         ` Jeff Garzik
2007-05-18 23:04         ` Christoph Hellwig
2007-05-21 14:56           ` James Ketrenos
2007-05-21 16:26             ` Christoph Hellwig
2007-05-21 16:48               ` James Ketrenos
2007-05-21 18:15                 ` Christoph Hellwig
2007-05-21 20:12                   ` Cohen, Guy
2007-05-21 21:02                     ` Jeff Garzik
2007-05-21 21:10                       ` Randy Dunlap
2007-05-21 21:43                         ` Cohen, Guy
2007-05-21 22:15                           ` Jeff Garzik
2007-05-21 21:22                     ` Joerg Mayer
2007-05-21 21:46                       ` Cohen, Guy
2007-05-18 22:13     ` Randy Dunlap
2007-05-18 23:05 ` [PATCH] Add iwlwifi wireless drivers Christoph Hellwig
2007-05-18 23:22   ` Michael Wu
2007-05-22 21:50 ` [PATCH v3] " James Ketrenos
2007-05-23  1:06   ` Jeff Garzik
2007-05-23 15:16     ` James Ketrenos

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=464BD9D4.4020909@linux.intel.com \
    --to=jketreno@linux.intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=randy.dunlap@oracle.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).