From: Kalle Valo <kalle.valo@iki.fi>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: Greg KH <greg@kroah.com>,
Xose Vazquez Perez <xose.vazquez@gmail.com>,
dcbw@redhat.com, linux-wireless <linux-wireless@vger.kernel.org>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH] Add vt6656 driver to drivers/staging.
Date: Thu, 16 Apr 2009 11:47:50 +0300 [thread overview]
Message-ID: <87zleh9e89.fsf@litku.valot.fi> (raw)
In-Reply-To: <73aaf0dd0904160139o159a604fv5b3ff0801124d1d3@mail.gmail.com> (Max Filippov's message of "Thu\, 16 Apr 2009 12\:39\:56 +0400")
Max Filippov <jcmvbkbc@gmail.com> writes:
>> I have received a report that at76_usb has worked better than
>> at76c50x-usb. Also p54spi implementation is quite new and not that much
>> tested.
>>
>> If it's ok for you, I would like to have both at76_usb and stlc45xx in
>> the staging area for some time still. I will let you know when they can
>> be removed.
>
> Kalle, what is the primary location for stlc45xx sources then?
I have been thinking about using staging the primary location. What do
you think?
> I see that version in staging is pretty old.
Yeah, I have been planning to patch bomb Greg at some point with all the
patches from the stlc45xx git tree. It's just that n800 support is
currently broken in 2.6.30-rc1 from linux-omap tree :(
--
Kalle Valo
next prev parent reply other threads:[~2009-04-16 8:47 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 19:16 [PATCH] Add vt6656 driver to drivers/staging Xose Vazquez Perez
2009-04-15 21:21 ` Greg KH
2009-04-16 5:58 ` Kalle Valo
2009-04-16 8:39 ` Max Filippov
2009-04-16 8:47 ` Kalle Valo [this message]
2009-04-16 9:14 ` Max Filippov
2009-04-16 9:52 ` Kalle Valo
2009-04-18 21:18 ` Ivo van Doorn
2009-04-20 13:59 ` John W. Linville
2009-04-21 10:30 ` Ivo Van Doorn
2009-04-21 12:42 ` Ivo Van Doorn
2009-04-21 13:53 ` John W. Linville
2009-04-21 13:52 ` John W. Linville
-- strict thread matches above, loose matches on Subject: below --
2009-04-14 10:52 Forest Bond
2009-04-14 11:07 ` Johannes Berg
2009-04-14 11:39 ` Forest Bond
2009-04-14 11:48 ` Johannes Berg
2009-04-14 12:28 ` Marcel Holtmann
2009-04-14 12:43 ` Johannes Berg
2009-04-14 13:02 ` John W. Linville
2009-04-14 14:19 ` Forest Bond
2009-04-15 1:10 ` Greg KH
2009-04-15 1:51 ` Forest Bond
2009-04-19 17:09 ` Forest Bond
2009-04-19 19:52 ` Larry Finger
2009-04-19 20:01 ` Forest Bond
2009-04-19 22:32 ` Greg KH
2009-04-24 11:03 ` Forest Bond
2009-04-24 14:44 ` Larry Finger
2009-04-24 14:54 ` Forest Bond
2009-04-24 22:58 ` Greg KH
2009-04-25 0:08 ` Forest Bond
2009-04-25 0:14 ` Greg KH
2009-04-15 15:43 ` Dan Williams
2009-04-16 2:51 ` Greg KH
2009-04-15 13:19 ` John W. Linville
2009-04-14 14:52 ` Forest Bond
[not found] ` <18916.37868.64939.574249@gargle.gargle.HOWL>
2009-04-14 15:26 ` John W. Linville
2009-06-01 16:35 ` Gábor Stefanik
2009-06-01 16:52 ` Forest Bond
2009-06-08 17:08 ` Olivier Blin
2009-06-08 17:45 ` Forest Bond
2009-06-08 18:01 ` Olivier Blin
[not found] <20090414024610.GA3924@storm.local.network>
2009-04-14 2:53 ` 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=87zleh9e89.fsf@litku.valot.fi \
--to=kalle.valo@iki.fi \
--cc=dcbw@redhat.com \
--cc=greg@kroah.com \
--cc=jcmvbkbc@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=xose.vazquez@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 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.