From: Kalle Valo <kalle.valo@iki.fi>
To: Javier Martinez Canillas <martinez.javier@gmail.com>
Cc: Christian Lamparter <chunkeey@googlemail.com>,
Greg KH <greg@kroah.com>,
"devel\@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/1] staging/stlc45xx: Fix compile error
Date: Fri, 16 Oct 2009 19:05:25 +0300 [thread overview]
Message-ID: <87iqefmiii.fsf@purkki.valot.fi> (raw)
In-Reply-To: <390803460910160859m6364219fx59fe067432a4942e@mail.gmail.com> (Javier Martinez Canillas's message of "Fri\, 16 Oct 2009 11\:59\:04 -0400")
Javier Martinez Canillas <martinez.javier@gmail.com> writes:
>>> At least I could make it compile when the API changes and work on bugs
>>> reported until you are confident that p54spi driver is good enough and
>>> there is no need anymore for stlc45xx.
>>
>> p54spi IS stlc45xx, but with a different name.
>
> In that case I guess probably the best option would be to remove
> stlc45xx from staging as Kalle sugested. Users should migrate to
> p54spi since it is already in /net/wireless/
Yes, p54spi is the future. If you have spare time, better to work on
p54spi instead of stlc45xx.
--
Kalle Valo
next prev parent reply other threads:[~2009-10-16 16:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1255575825.10636.17.camel@laptop>
[not found] ` <20091015031138.GB16633@kroah.com>
2009-10-16 7:13 ` [PATCH 1/1] staging/stlc45xx: Fix compile error Kalle Valo
2009-10-16 14:11 ` Javier Martinez Canillas
2009-10-16 14:54 ` Christian Lamparter
2009-10-16 15:59 ` Javier Martinez Canillas
2009-10-16 16:01 ` Greg KH
2009-10-16 16:05 ` Kalle Valo [this message]
2009-10-16 15:23 ` Greg KH
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=87iqefmiii.fsf@purkki.valot.fi \
--to=kalle.valo@iki.fi \
--cc=chunkeey@googlemail.com \
--cc=devel@driverdev.osuosl.org \
--cc=greg@kroah.com \
--cc=linux-wireless@vger.kernel.org \
--cc=martinez.javier@gmail.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 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).