From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Stanislav Yakovlev <stas.yakovlev@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
Tom Gundersen <teg@jklm.no>, Wey-Yi Guy <wey-yi.w.guy@intel.com>,
linux-wireless@vger.kernel.org,
Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: MAINTAINER NEEDED -- Re: status of ipw2x00
Date: Thu, 15 Mar 2012 12:02:20 +0100 [thread overview]
Message-ID: <20120315110219.GA2335@redhat.com> (raw)
In-Reply-To: <CA++WF2PnEzS5CAfryaPrJSs3Xb3s0WK1zR7N5o8+ud2HiU5GCw@mail.gmail.com>
On Fri, Feb 03, 2012 at 11:58:03PM +0300, Stanislav Yakovlev wrote:
> Hi John,
>
> On 30 January 2012 21:44, John W. Linville <linville@tuxdriver.com> wrote:
> > On Mon, Jan 30, 2012 at 02:42:52PM +0100, Tom Gundersen wrote:
> >
> >> If we are not able to drop the 2x00 drivers, are anyone still
> >> interested in working on them to fix the firmware loading?
> >
> > Anyone out there looking for a project? A way to "break-in" to the
> > public Linux community without the risk of breaking anything too
> > important? :-)
> >
> > If someone wants to be the ipw2x00 maintainer, all they need to do
> > is start sending some non-broken patches...
>
> I would volunteer taking ipw2x00 driver maintenance if it is ok with everyone.
Hi Stanislav
Perhaps you should post a patch that change ipw2x00 entry on MAINTAINERS
file.
Are you plan to fix issues caused on current firmware loading changes on
linux ? We have a few bug reports about that:
https://bugzilla.redhat.com/show_bug.cgi?id=783708
https://bugzilla.redhat.com/show_bug.cgi?id=802106
Stanislaw
next prev parent reply other threads:[~2012-03-15 11:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 13:42 status of ipw2x00 Tom Gundersen
2012-01-30 14:55 ` Johannes Berg
2012-01-30 15:08 ` Tom Gundersen
2012-01-30 15:28 ` wwguy
2012-01-30 18:44 ` MAINTAINER NEEDED -- " John W. Linville
2012-01-30 19:55 ` Dan Williams
2012-01-30 20:13 ` Florian Fainelli
2012-01-30 20:23 ` Dan Williams
2012-01-30 21:47 ` Julian Calaby
2012-01-30 21:52 ` Florian Fainelli
2012-01-30 21:59 ` Julian Calaby
2012-02-02 10:42 ` Francois Romieu
2012-02-03 20:58 ` Stanislav Yakovlev
2012-02-07 21:27 ` yao zhao
2012-03-15 11:02 ` Stanislaw Gruszka [this message]
2012-03-16 4:02 ` Stanislav Yakovlev
2012-03-17 14:36 ` Henrique de Moraes Holschuh
2012-03-19 22:56 ` Stanislav Yakovlev
2012-03-19 23:01 ` Julian Calaby
2012-03-20 2:11 ` Henrique de Moraes Holschuh
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=20120315110219.GA2335@redhat.com \
--to=sgruszka@redhat.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=stas.yakovlev@gmail.com \
--cc=teg@jklm.no \
--cc=wey-yi.w.guy@intel.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.