From: Michael Buesch <mb@bu3sch.de>
To: Stefano Brivio <stefano.brivio@polimi.it>
Cc: "John W. Linville" <linville@tuxdriver.com>,
davem@davemloft.net, netdev@vger.kernel.org,
linux-wireless@vger.kernel.org
Subject: Re: pull request: wireless-2.6 'upstream' 2008-01-22
Date: Wed, 23 Jan 2008 12:30:07 +0100 [thread overview]
Message-ID: <200801231230.07734.mb@bu3sch.de> (raw)
In-Reply-To: <20080123121551.4586e706@morte>
On Wednesday 23 January 2008 12:15:51 Stefano Brivio wrote:
> On Tue, 22 Jan 2008 20:45:21 -0500
> "John W. Linville" <linville@tuxdriver.com> wrote:
>
> > b43legacy: Remove the PHY spinlock
>
> I hope you tested this. I still haven't been able to (I received the
> needed hardware yesterday), and Michael said that the patch has been
> compile-tested only.
John, if we use subject lines such as:
[PATCH RFT] foobar: bizbaz
That means the patch is _not_ submitted for inclusion, yet.
The RFT means Request-For-Testing. Ususally, if I send out such
patches, they are completely untested. I usually compiletest them,
but that's it.
But in future I can also put a comment into the mailbody that
explains why to not apply it, yet.
For this particular patch, please leave it in now. I'm pretty
sure it is correct. So actual testing will be done upstream now. ;)
--
Greetings Michael.
next prev parent reply other threads:[~2008-01-23 11:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 1:45 pull request: wireless-2.6 'upstream' 2008-01-22 John W. Linville
2008-01-23 3:04 ` David Miller
[not found] ` <20080123014521.GG3206-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2008-01-23 11:15 ` Stefano Brivio
2008-01-23 11:30 ` Michael Buesch [this message]
[not found] ` <200801231230.07734.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2008-01-23 12:46 ` John W. Linville
2008-01-23 12:41 ` John W. Linville
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=200801231230.07734.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=davem@davemloft.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=stefano.brivio@polimi.it \
/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).