From: "John W. Linville" <linville@tuxdriver.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
linux-next@vger.kernel.org, kernel-janitors@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [ANNOUNCE] linux-staging tree created
Date: Fri, 13 Jun 2008 14:33:29 +0000 [thread overview]
Message-ID: <20080613143328.GA16506@tuxdriver.com> (raw)
In-Reply-To: <43e72e890806130714k535b041evaf750209ea492c47@mail.gmail.com>
On Fri, Jun 13, 2008 at 07:14:32AM -0700, Luis R. Rodriguez wrote:
> This is great. To let this be useful for wireless we'll need
> wireless-testing.git merged as we rely on it for the latest and
> greatest. Is this a possibility?
> We have a few drivers which are not yet ready for
> wireless-testing.git. Airgo is one.
>
> Anyway, good stuff. Let me know what you think about letting this work
> for wireless too.
I don't think directly pulling wireless-testing is a good idea of
-staging for process-related reasons. However I think we can arrange
to send something for the new tree. at76, airgo, and mrv8k are all
decent candidates.
Greg, how does the -staging tree get managed? Is it periodically
rebuilt (like -next)? Or would I need to send you pull requests?
John
--
John W. Linville
linville@tuxdriver.com
WARNING: multiple messages have this Message-ID (diff)
From: "John W. Linville" <linville@tuxdriver.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
linux-next@vger.kernel.org, kernel-janitors@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [ANNOUNCE] linux-staging tree created
Date: Fri, 13 Jun 2008 10:33:29 -0400 [thread overview]
Message-ID: <20080613143328.GA16506@tuxdriver.com> (raw)
In-Reply-To: <43e72e890806130714k535b041evaf750209ea492c47@mail.gmail.com>
On Fri, Jun 13, 2008 at 07:14:32AM -0700, Luis R. Rodriguez wrote:
> This is great. To let this be useful for wireless we'll need
> wireless-testing.git merged as we rely on it for the latest and
> greatest. Is this a possibility?
> We have a few drivers which are not yet ready for
> wireless-testing.git. Airgo is one.
>
> Anyway, good stuff. Let me know what you think about letting this work
> for wireless too.
I don't think directly pulling wireless-testing is a good idea of
-staging for process-related reasons. However I think we can arrange
to send something for the new tree. at76, airgo, and mrv8k are all
decent candidates.
Greg, how does the -staging tree get managed? Is it periodically
rebuilt (like -next)? Or would I need to send you pull requests?
John
--
John W. Linville
linville@tuxdriver.com
WARNING: multiple messages have this Message-ID (diff)
From: "John W. Linville" <linville@tuxdriver.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
linux-next@vger.kernel.org, kernel-janitors@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [ANNOUNCE] linux-staging tree created
Date: Fri, 13 Jun 2008 10:33:29 -0400 [thread overview]
Message-ID: <20080613143328.GA16506@tuxdriver.com> (raw)
In-Reply-To: <43e72e890806130714k535b041evaf750209ea492c47@mail.gmail.com>
On Fri, Jun 13, 2008 at 07:14:32AM -0700, Luis R. Rodriguez wrote:
> This is great. To let this be useful for wireless we'll need
> wireless-testing.git merged as we rely on it for the latest and
> greatest. Is this a possibility?
> We have a few drivers which are not yet ready for
> wireless-testing.git. Airgo is one.
>
> Anyway, good stuff. Let me know what you think about letting this work
> for wireless too.
I don't think directly pulling wireless-testing is a good idea of
-staging for process-related reasons. However I think we can arrange
to send something for the new tree. at76, airgo, and mrv8k are all
decent candidates.
Greg, how does the -staging tree get managed? Is it periodically
rebuilt (like -next)? Or would I need to send you pull requests?
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2008-06-13 14:33 UTC|newest]
Thread overview: 87+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 19:05 [ANNOUNCE] linux-staging tree created Greg KH
2008-06-10 19:05 ` Greg KH
2008-06-10 19:05 ` Greg KH
2008-06-10 19:06 ` linux-staging status for June 10, 2008 Greg KH
2008-06-10 19:06 ` Greg KH
2008-06-10 19:06 ` Greg KH
2008-06-10 22:52 ` [ANNOUNCE] linux-staging tree created Theodore Tso
2008-06-10 23:05 ` Greg KH
2008-06-11 0:07 ` Felipe Balbi
2008-06-11 0:07 ` Felipe Balbi
2008-06-11 0:07 ` Felipe Balbi
2008-06-11 3:28 ` Greg KH
2008-06-11 3:28 ` Greg KH
2008-06-11 3:28 ` Greg KH
2008-06-11 1:05 ` Nigel Cunningham
2008-06-11 1:05 ` Nigel Cunningham
2008-06-11 1:05 ` Nigel Cunningham
2008-06-11 3:29 ` Greg KH
2008-06-11 3:29 ` Greg KH
2008-06-11 3:29 ` Greg KH
2008-06-11 3:57 ` Nigel Cunningham
2008-06-11 4:00 ` Nigel Cunningham
2008-06-11 4:00 ` Nigel Cunningham
2008-06-11 16:24 ` Greg KH
2008-06-11 16:24 ` Greg KH
2008-06-11 16:24 ` Greg KH
2008-06-11 4:03 ` Template of what you're after? (Was [ANNOUNCE] linux-staging tree Nigel Cunningham
2008-06-11 4:03 ` Template of what you're after? (Was [ANNOUNCE] linux-staging tree created) Nigel Cunningham
2008-06-11 4:03 ` Nigel Cunningham
2008-06-11 16:23 ` Template of what you're after? (Was [ANNOUNCE] linux-staging Greg KH
2008-06-11 16:23 ` Template of what you're after? (Was [ANNOUNCE] linux-staging tree created) Greg KH
2008-06-11 16:23 ` Greg KH
2008-06-11 9:27 ` [ANNOUNCE] linux-staging tree created Benny Halevy
2008-06-11 9:27 ` Benny Halevy
2008-06-11 9:27 ` Benny Halevy
2008-06-11 9:50 ` Boaz Harrosh
2008-06-11 9:50 ` Boaz Harrosh
2008-06-11 9:58 ` Felipe Balbi
2008-06-11 9:58 ` Felipe Balbi
2008-06-11 16:25 ` Greg KH
2008-06-11 16:25 ` Greg KH
2008-06-11 17:43 ` Boaz Harrosh
2008-06-11 17:43 ` Boaz Harrosh
2008-06-11 16:25 ` Greg KH
2008-06-11 16:25 ` Greg KH
2008-06-11 16:25 ` Greg KH
2008-06-11 10:45 ` Will Newton
2008-06-11 10:45 ` Will Newton
2008-06-11 10:45 ` Will Newton
2008-06-11 16:26 ` Greg KH
2008-06-11 16:26 ` Greg KH
2008-06-11 16:26 ` Greg KH
2008-06-12 11:37 ` Will Newton
2008-06-12 11:37 ` Will Newton
2008-06-12 11:37 ` Will Newton
2008-06-12 23:54 ` Greg KH
2008-06-12 23:54 ` Greg KH
2008-06-12 23:54 ` Greg KH
2008-06-13 14:14 ` Luis R. Rodriguez
2008-06-13 14:14 ` Luis R. Rodriguez
2008-06-13 14:14 ` Luis R. Rodriguez
2008-06-13 14:33 ` John W. Linville [this message]
2008-06-13 14:33 ` John W. Linville
2008-06-13 14:33 ` John W. Linville
2008-06-13 15:51 ` Luis R. Rodriguez
2008-06-13 15:51 ` Luis R. Rodriguez
2008-06-13 15:51 ` Luis R. Rodriguez
[not found] ` <20080613143328.GA16506-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2008-06-14 0:28 ` Greg KH
2008-06-14 0:28 ` Greg KH
2008-06-14 0:28 ` Greg KH
2008-06-14 0:28 ` Greg KH
[not found] ` <43e72e890806130714k535b041evaf750209ea492c47-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-14 0:27 ` Greg KH
2008-06-14 0:27 ` Greg KH
2008-06-14 0:27 ` Greg KH
2008-06-14 0:27 ` Greg KH
2008-06-17 12:51 ` Pavel Machek
2008-06-17 12:51 ` Pavel Machek
2008-06-17 12:51 ` Pavel Machek
2008-07-02 23:11 ` Greg KH
2008-07-02 23:11 ` Greg KH
2008-07-02 23:11 ` Greg KH
2008-07-14 2:50 ` Jike Song
2008-07-14 2:50 ` Jike Song
2008-07-14 2:50 ` Jike Song
2008-07-14 2:56 ` Greg KH
2008-07-14 2:56 ` Greg KH
2008-07-14 2:56 ` 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=20080613143328.GA16506@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=devel@linuxdriverproject.org \
--cc=greg@kroah.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=sfr@canb.auug.org.au \
/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.