All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org,
	linville@tuxdriver.com, jirislaby@gmail.com, mcgrof@gmail.com,
	Nick Kossifidis <mickflemm@gmail.com>
Subject: Re: [PATCH 12/12] ath5k: Fix a compilation error after reg list update
Date: Tue, 22 Jul 2008 16:53:27 +0200	[thread overview]
Message-ID: <4885F467.2040606@gmail.com> (raw)
In-Reply-To: <20080720035221.GL7440@makis>

Why the hell the mailer cropped Nick's address away...

On 07/20/2008 05:52 AM, Nick Kossifidis wrote:
>  Last minute fix...
> 
>  AR5K_CPCORN is changed to AR5K_CPCOVF in reg list update so we have to update debug.c in order to compile
> 
>  Changes-licensed-under: ISC
>  Signed-off-by: Nick Kossifidis <mickflemm@gmail.com>
> 
> ---
> diff --git a/drivers/net/wireless/ath5k/debug.c b/drivers/net/wireless/ath5k/debug.c
> index 41d5fa3..6fa6c8e 100644
> --- a/drivers/net/wireless/ath5k/debug.c
> +++ b/drivers/net/wireless/ath5k/debug.c
> @@ -129,7 +129,7 @@ static struct reg regs[] = {
>  	REG_STRUCT_INIT(AR5K_CPC1),
>  	REG_STRUCT_INIT(AR5K_CPC2),
>  	REG_STRUCT_INIT(AR5K_CPC3),
> -	REG_STRUCT_INIT(AR5K_CPCORN),
> +	REG_STRUCT_INIT(AR5K_CPCOVF),
>  	REG_STRUCT_INIT(AR5K_RESET_CTL),
>  	REG_STRUCT_INIT(AR5K_SLEEP_CTL),
>  	REG_STRUCT_INIT(AR5K_INTPEND),

Please amend this to the patch 1 to not break bisectability.

      parent reply	other threads:[~2008-07-22 14:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-20  3:52 [PATCH 12/12] ath5k: Fix a compilation error after reg list update Nick Kossifidis
2008-07-22 14:36 ` Jiri Slaby
2008-07-28 13:04   ` [ath5k-devel] " Nick Kossifidis
2008-07-28 13:10     ` Pavel Roskin
2008-07-28 14:44       ` Nick Kossifidis
2008-07-22 14:53 ` Jiri Slaby [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=4885F467.2040606@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=ath5k-devel@lists.ath5k.org \
    --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 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.