netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: davem@davemloft.net, linux-wireless@vger.kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	me@bobcopeland.com
Subject: Re: pull request: wireless-2.6 2008-10-29
Date: Wed, 29 Oct 2008 16:23:24 -0700	[thread overview]
Message-ID: <20081029162324.28f5864d@infradead.org> (raw)
In-Reply-To: <20081029231855.GD3485@tuxdriver.com>

On Wed, 29 Oct 2008 19:18:55 -0400
"John W. Linville" <linville@tuxdriver.com> wrote:

> Dave,
> 
> Another quick round of fixes intended for 2.6.28...
> 
> This includes fixes for bugs 11749 and 11845, fixes a reset-related
> regression in ath5k, fixes a Kconfig-related error for rt2x00, and
> fixes some sparse warnings and a possible buffer overrun in libertas.
> Also, it corrects a spelling error and marks Bob Copeland as an
> ath5k maintainer.

speaking of ath5k:

http://www.kerneloops.org/version.php?start=1835008&end=1867775&version=28-rc

it seems to have added a few WARN_ON()s which now end up at the top of
the list .. are these known or should I spend some time writing reports
for netdev ?

  reply	other threads:[~2008-10-29 23:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-29 23:18 pull request: wireless-2.6 2008-10-29 John W. Linville
2008-10-29 23:23 ` Arjan van de Ven [this message]
     [not found]   ` <20081029162324.28f5864d-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2008-10-29 23:33     ` John W. Linville
     [not found]       ` <20081029233350.GE3485-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2008-10-30  1:19         ` Bob Copeland
2008-10-30  4:00           ` Arjan van de Ven
2008-10-30 14:48         ` Stefan Hellermann
2008-10-30 16:17           ` Bob Copeland
     [not found] ` <20081029231855.GD3485-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2008-10-29 23:40   ` Elias Oltmanns
2008-10-31  6:49   ` David Miller

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=20081029162324.28f5864d@infradead.org \
    --to=arjan@infradead.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=me@bobcopeland.com \
    --cc=netdev@vger.kernel.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).