From: Jiri Slaby <jirislaby@gmail.com>
To: Nick Kossifidis <mickflemm@gmail.com>
Cc: "Luis R. Rodriguez" <mcgrof@winlab.rutgers.edu>,
ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org,
linville@tuxdriver.com, bruno@thinktube.com,
johannes@sipsolutions.net
Subject: Re: [ath5k-devel] [PATCH] ath5k: Port to new bitrate/channel API
Date: Thu, 31 Jan 2008 17:41:43 +0100 [thread overview]
Message-ID: <47A1FA47.2020801@gmail.com> (raw)
In-Reply-To: <40f31dec0801310816p3592bea0od2a19e0b15312e61@mail.gmail.com>
On 01/31/2008 05:16 PM, Nick Kossifidis wrote:
> Checkpatch shows up 40 points, most of them because it's over 80 lines
> and some of them because there are some missing spaces etc. I'm sure
> code is full of those so i believe we should better cleanup the whole
> code (also doing some sparse checking btw) once and for all (i told
> you in my previous mail that's what i want to do when i'm done with
> exams). It's really more easy for me to clean up the whole code after
> i'm done with exams than try to locate 40 places in this monster that
> might be fixed manually. I just need some time, i thought porting to
> the new API was urgent so i gave it full priority, cleanup can wait i
> guess (and we have to do it right and cautious).
It's fine to me.
next prev parent reply other threads:[~2008-01-31 16:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 18:38 [PATCH] ath5k: Port to new bitrate/channel API Nick Kossifidis
2008-01-30 18:43 ` [ath5k-devel] " Nick Kossifidis
2008-01-30 19:28 ` Jiri Slaby
2008-01-31 15:07 ` Luis R. Rodriguez
2008-01-31 15:32 ` [ath5k-devel] " Nick Kossifidis
2008-01-31 15:50 ` Luis R. Rodriguez
2008-01-31 16:16 ` Nick Kossifidis
2008-01-31 16:41 ` Jiri Slaby [this message]
2008-02-12 9:51 ` bruno randolf
2008-02-12 10:06 ` Nick Kossifidis
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=47A1FA47.2020801@gmail.com \
--to=jirislaby@gmail.com \
--cc=ath5k-devel@lists.ath5k.org \
--cc=bruno@thinktube.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@winlab.rutgers.edu \
--cc=mickflemm@gmail.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.