All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH v3 3/4] ath5k: define ath_common ops
Date: Mon, 14 Sep 2009 11:10:58 +0200	[thread overview]
Message-ID: <4AAE08A2.9080504@gmail.com> (raw)
In-Reply-To: <1252919221-13628-1-git-send-email-lrodriguez@atheros.com>

On 09/14/2009 11:07 AM, Luis R. Rodriguez wrote:
> Only common ath read/write ops go through the common ops.
> 
> Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
> ---
> 
> Here's a respin of 3/4 based on Jiri's comments.

Thanks.

Acked-by: Jiri Slaby <jirislaby@gmail.com>

WARNING: multiple messages have this Message-ID (diff)
From: Jiri Slaby <jirislaby@gmail.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: linville@tuxdriver.com, devel@linuxdriverproject.org,
	ath9k-devel@lists.ath9k.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v3 3/4] ath5k: define ath_common ops
Date: Mon, 14 Sep 2009 11:10:58 +0200	[thread overview]
Message-ID: <4AAE08A2.9080504@gmail.com> (raw)
In-Reply-To: <1252919221-13628-1-git-send-email-lrodriguez@atheros.com>

On 09/14/2009 11:07 AM, Luis R. Rodriguez wrote:
> Only common ath read/write ops go through the common ops.
> 
> Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
> ---
> 
> Here's a respin of 3/4 based on Jiri's comments.

Thanks.

Acked-by: Jiri Slaby <jirislaby@gmail.com>

  reply	other threads:[~2009-09-14  9:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-14  9:07 [ath9k-devel] [PATCH v3 3/4] ath5k: define ath_common ops Luis R. Rodriguez
2009-09-14  9:07 ` Luis R. Rodriguez
2009-09-14  9:10 ` Jiri Slaby [this message]
2009-09-14  9:10   ` Jiri Slaby
2009-09-14 18:12 ` [ath9k-devel] " Bob Copeland
2009-09-14 18:12   ` Bob Copeland

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=4AAE08A2.9080504@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=ath9k-devel@lists.ath9k.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 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.