From: "Jouni Malinen" <jkm@devicescape.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Dan Williams <dcbw@redhat.com>,
John Linville <linville@tuxdriver.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH 1/8] d80211/bcm43xx: Modify struct ieee80211_rx_status for wireless statistics.
Date: Wed, 9 Aug 2006 13:34:33 -0700 [thread overview]
Message-ID: <20060809203433.GM26616@instant802.com> (raw)
In-Reply-To: <44D9FD6C.9030006@lwfinger.net>
On Wed, Aug 09, 2006 at 10:21:16AM -0500, Larry Finger wrote:
> Dan Williams wrote:
> >> int ssi;
> >>+ int maxssi;
> >Spacing? Looks like you're using real tabs here, but the current code
> >uses 8 spaces instead. Not sure if that's a problem.
>
> I am using tabs, which I think is the preferred way. I also remember that
> the rule is not to change the white space on things you are not touching.
> Is that correct?
That's at least the way I would prefer to do this. Unrelated whitespace
changes as part of a patch are almost always bad and large patch of
modifying just the whitespaces around the tree is likely to add large
number of conflicts for pending work that goes on at the moment.
Unfortunately, I forgot to replace this part when making the initial
release of the Devicescape stack. I've always used tabs myself, but some
of the areas of the code that I did not write was done using spaces.
Anyway, this should move to using tabs over time whenever source code is
being modified.
--
Jouni Malinen PGP id EFC895FA
prev parent reply other threads:[~2006-08-09 20:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 23:58 [PATCH 1/8] d80211/bcm43xx: Modify struct ieee80211_rx_status for wireless statistics Larry Finger
2006-08-09 14:22 ` Dan Williams
2006-08-09 15:21 ` Larry Finger
2006-08-09 20:34 ` Jouni Malinen [this message]
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=20060809203433.GM26616@instant802.com \
--to=jkm@devicescape.com \
--cc=Larry.Finger@lwfinger.net \
--cc=dcbw@redhat.com \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
/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).