James Ketrenos wrote:
Jeff Garzik wrote:
It seems like some of this overlaps changes already in upstream.
What's the best way to start this process? I would prefer to receive
patches rather than 'git pull' at the present time.
Understood.
Should I Lindent the files first?
Probably cleanest that way. I've been passing the net/ieee80211/*.c and
include/net/ieee80211*.h files through the following script:
#!/usr/bin/env bash
scripts/Lindent $@
for file in $@; do
sed -i -e "s:\ *\$::g" -e "s:\t*\$::g" $file;
done
I don't know if Lindent strips trailing whitespace, so I stuck the sed
in there for good measure.
Would you rather just start sending those 50+ patches?
I can pull netdev-2.6#ieee80211 once you have a Lindent'd version and I
can then (hopefully) run my rebase scripts, weeding out dups, and can
then send the patches out.
FWIW now that upstream has ieee80211, the branch is gone from
netdev-2.6. ieee80211/ipw changes will usually go straight into the
'upstream' branch that I send to Andrew/Linus on a regular basis.
As of this writing, -all- ieee80211 patches have been committed
upstream, and appear in Linus's linux-2.6.git tree. Including the
Lindent change.
Feel free to start submitting patches, diff'd against the latest upstream.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
