All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Andrey Yurovsky <andrey@cozybit.com>
Cc: Bob Copeland <me@bobcopeland.com>, Keir <keirlawson@gmail.com>,
	linux-wireless@vger.kernel.org
Subject: Re: ath5k mesh in 2.6.28?
Date: Tue, 27 Jan 2009 17:38:52 -0800	[thread overview]
Message-ID: <20090128013852.GB12223@kroah.com> (raw)
In-Reply-To: <45e8e6c40901230929r6efbf19xbe2c32bef92db8e@mail.gmail.com>

On Fri, Jan 23, 2009 at 09:29:22AM -0800, Andrey Yurovsky wrote:
> Sorry, looks like that's my mistake (I thought the patch had made it
> in).  Greg -- thanks for queuing the patch.
> 
> For completeness, I should note that ath5k mesh is later broken by
> "ath5k: Update PCU code" and fixed again (hopefully both in by
> 2.6.29!) by "ath5k: Correct usage of AR5K_CFG_ADHOC"
> 
> Greg and Keir -- I also suggest Brian's patch, "mac80211: decrement
> ref count to netdev after launching mesh discovery", commit
> 05188d21d21dc8976bff13a9ca73a230eef86d40 for stable as it should apply
> there and fixes a bug that will sometimes prevent module unload if a
> mesh interface was active.

I think you mean 5dc306f3bd1d4cfdf79df39221b3036eab1ddcf3 instead, there
is no 05188d21d21dc8976bff13a9ca73a230eef86d40 in Linus's tree :)

queued up,

greg k-h

      parent reply	other threads:[~2009-01-28  2:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-23 13:30 ath5k mesh in 2.6.28? Keir
2009-01-23 15:17 ` Bob Copeland
2009-01-23 15:25   ` Keir
2009-01-23 16:26     ` Bob Copeland
2009-01-23 17:09       ` [stable] " Greg KH
2009-01-28  1:36       ` Greg KH
2009-01-23 17:29   ` Andrey Yurovsky
2009-01-23 17:40     ` Greg KH
2009-01-23 18:50       ` Andrey Yurovsky
2009-01-28  1:38     ` Greg KH [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=20090128013852.GB12223@kroah.com \
    --to=greg@kroah.com \
    --cc=andrey@cozybit.com \
    --cc=keirlawson@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=me@bobcopeland.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.