Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: 2.6.33-rc7: Reported regressions from 2.6.32
Date: Mon, 8 Feb 2010 10:24:15 -0800	[thread overview]
Message-ID: <43e72e891002081024id33b99ai61118370a6d81db9@mail.gmail.com> (raw)
In-Reply-To: <4Ht3jFrT7uE.A.JI.-nzbLB@chimera>

On Sun, Feb 7, 2010 at 2:16 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> [ANNOUNCEMENT:
>  Maciej Rutecki has generously volunteered to work on the tracking of kernel
>  regressions with me, so now there are two people doing this and I'm going
>  to call us "the tracking team".  Please be friendly to Maciej, he's doing his
>  best to help.  If you have any information about kernel regressions you want
>  to share with us, please feel free to contact Maciej as well as me.]
>
> This message contains a list of some regressions from 2.6.32,
> for which there are no fixes in the mainline known to the tracking team.
> If any of them have been fixed already, please let us know.
>
> If you know of any other unresolved regressions from 2.6.32, please let us
> know either and we'll add them to the list.  Also, please let us know
> if any of the entries below are invalid.
>
> Each entry from the list will be sent additionally in an automatic reply
> to this message with CCs to the people involved in reporting and handling
> the issue.
>
>
> Listed regressions statistics:

No wireless regressions :D

  Luis

      reply	other threads:[~2010-02-08 18:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-07 22:16 2.6.33-rc7: Reported regressions from 2.6.32 Rafael J. Wysocki
2010-02-08 18:24 ` Luis R. Rodriguez [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=43e72e891002081024id33b99ai61118370a6d81db9@mail.gmail.com \
    --to=mcgrof@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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