linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bruno randolf <bruno@thinktube.com>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: ath5k-devel@lists.ath5k.org, mcgrof@gmail.com,
	mickflemm@gmail.com, linux-wireless@vger.kernel.org,
	linville@tuxdriver.com
Subject: Re: [PATCH 6/6] ath5k: simplify beacon configuration
Date: Wed, 9 Jan 2008 18:37:40 +0900	[thread overview]
Message-ID: <200801091837.41102.bruno@thinktube.com> (raw)
In-Reply-To: <47849498.5070605@gmail.com>

On Wednesday 09 January 2008 18:32:08 Jiri Slaby wrote:
> checkpatch doesn't like this, please put the else path next time on the
> same line as } is.

oh, sorry i forgot checkpatch this time. i will resend.

bruno

  reply	other threads:[~2008-01-09  9:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-09  9:16 ath5k: beacon patches Bruno Randolf
2008-01-09  9:16 ` [PATCH 1/6] ath5k: code cosmetics Bruno Randolf
2008-01-09  9:16   ` [PATCH 2/6] ath5k: rename function ath5k_hw_wait_for_beacon Bruno Randolf
2008-01-09  9:16     ` [PATCH 3/6] ath5k: comment out unused beacon functions and structures Bruno Randolf
2008-01-09  9:16       ` [PATCH 4/6] ath5k: centrally define TSF to TU conversion macro Bruno Randolf
2008-01-09  9:16         ` [PATCH 5/6] ath5k: configure beacons Bruno Randolf
2008-01-09  9:16           ` [PATCH 6/6] ath5k: simplify beacon configuration Bruno Randolf
2008-01-09  9:32             ` Jiri Slaby
2008-01-09  9:37               ` bruno randolf [this message]
2008-01-09 10:11                 ` [PATCH] " Bruno Randolf
2008-01-10 20:21       ` [PATCH 3/6] ath5k: comment out unused beacon functions and structures Luis R. Rodriguez
2008-01-10  0:54   ` [PATCH 1/6] ath5k: code cosmetics Johannes Berg
2008-01-10 13:42     ` Nick Kossifidis
2008-01-10 13:46       ` Johannes Berg

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=200801091837.41102.bruno@thinktube.com \
    --to=bruno@thinktube.com \
    --cc=ath5k-devel@lists.ath5k.org \
    --cc=jirislaby@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mcgrof@gmail.com \
    --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 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).