linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bob Copeland <me@bobcopeland.com>
To: Nick Kossifidis <mickflemm@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>,
	jirislaby@gmail.com, lrodriguez@atheros.com,
	linux-wireless@vger.kernel.org, ath5k-devel@lists.ath5k.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] ath5k: prevent infinite loop
Date: Tue, 19 May 2009 07:42:40 -0400	[thread overview]
Message-ID: <20090519114240.GA13934@hash.localnet> (raw)
In-Reply-To: <40f31dec0905182332v49aff368oe485efaa56fbc11a@mail.gmail.com>

On Tue, May 19, 2009 at 09:32:42AM +0300, Nick Kossifidis wrote:
> >> http://git.kernel.org/?p=linux/kernel/git/linville/wireless-testing.git;a=blob;f=drivers/net/wireless/ath/ath5k/phy.c;h=d0d1c350025aebba1fe4e17a44550536a59951ba;hb=HEAD

> -> http://git.kernel.org/?p=linux/kernel/git/linville/wireless-testing.git;a=blob;f=drivers/net/wireless/ath/ath5k/eeprom.c;h=c56b494d417acd40d445d922f2861b53cc2315df;hb=HEAD#l910

Do these patches need to go to 2.6.30?

-- 
Bob Copeland %% www.bobcopeland.com


  parent reply	other threads:[~2009-05-19 11:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-19  0:28 [PATCH] ath5k: prevent infinite loop Steven Rostedt
2009-05-19  0:34 ` Nick Kossifidis
2009-05-19  0:43   ` Steven Rostedt
2009-05-19  6:32     ` Nick Kossifidis
2009-05-19  6:39       ` [ath5k-devel] " Luis R. Rodriguez
2009-05-19 11:45         ` Steven Rostedt
2009-05-19 16:38           ` Luis R. Rodriguez
2009-05-19 11:42       ` Bob Copeland [this message]
2009-05-19 11:54         ` Steven Rostedt
2009-05-19 12:34           ` Bob Copeland
2009-05-20  3:37           ` [PATCH] ath5k: avoid and warn on potential " 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=20090519114240.GA13934@hash.localnet \
    --to=me@bobcopeland.com \
    --cc=akpm@linux-foundation.org \
    --cc=ath5k-devel@lists.ath5k.org \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lrodriguez@atheros.com \
    --cc=mickflemm@gmail.com \
    --cc=rostedt@goodmis.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 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).