From: "Rafał Miłecki" <zajec5@gmail.com>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
b43-dev@lists.infradead.org
Subject: Re: [PATCH 0/2] ssb: updates matching specs, fix for hangs?
Date: Sun, 20 Jun 2010 14:56:09 +0200 [thread overview]
Message-ID: <AANLkTilYIRMalJXji9OCerjSdZJpj45JNa8XngKB9eyC@mail.gmail.com> (raw)
In-Reply-To: <4C1E0C5E.7070407@hauke-m.de>
W dniu 20 czerwca 2010 14:41 użytkownik Hauke Mehrtens
<hauke@hauke-m.de> napisał:
> Am 20.06.2010 14:34, schrieb Rafał Miłecki:
>> W dniu 24 maja 2010 21:50 użytkownik Rafał Miłecki <zajec5@gmail.com> napisał:
>>> John, I don't really know w-t policy, so please decide where we should apply
>>> these patches. I'll try to provide some description.
>>
>> John, I think you missed that two patches. It was already some time
>> ago, but AFAIR there wasn't any reason against commiting them, am I
>> wrong here?
>>
> Hi Rafał,
>
> They are aleardy in the wireless-next-2.6 tree and in linux-next:
>
> http://git.kernel.org/?p=linux/kernel/git/linville/wireless-next-2.6.git;a=commitdiff;h=fd515941cfaf949b55086a36943afe085d7268e6
>
> http://git.kernel.org/?p=linux/kernel/git/linville/wireless-next-2.6.git;a=commitdiff;h=c35deb4e70d52ed564c58569fe059dd7ca5f4eec
Whoops, OK, thanks for pointing. I just checked Linus's git and
wireless-testing.
--
Rafał
next prev parent reply other threads:[~2010-06-20 12:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 19:50 [PATCH 0/2] ssb: updates matching specs, fix for hangs? Rafał Miłecki
2010-05-24 19:50 ` [PATCH 1/2] ssb: update PMU init to match specs Rafał Miłecki
2010-05-24 19:50 ` [PATCH 2/2] ssb: fast powerup delay calculation for PMU capable devices Rafał Miłecki
2010-06-20 12:34 ` [PATCH 0/2] ssb: updates matching specs, fix for hangs? Rafał Miłecki
2010-06-20 12:41 ` Hauke Mehrtens
2010-06-20 12:56 ` Rafał Miłecki [this message]
2010-06-20 16:20 ` John W. Linville
2010-06-20 18:28 ` Rafał Miłecki
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=AANLkTilYIRMalJXji9OCerjSdZJpj45JNa8XngKB9eyC@mail.gmail.com \
--to=zajec5@gmail.com \
--cc=b43-dev@lists.infradead.org \
--cc=hauke@hauke-m.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).