From: Kalle Valo <kvalo@adurom.com>
To: "Arend van Spriel" <arend@broadcom.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org,
"David Miller" <davem@davemloft.net>
Subject: Re: [PATCH] brcmsmac: disable power-save related functions
Date: Wed, 05 Jun 2013 11:44:07 +0300 [thread overview]
Message-ID: <874ndd3q20.fsf@purkki.adurom.net> (raw)
In-Reply-To: <878v2p3qst.fsf@purkki.adurom.net> (Kalle Valo's message of "Wed, 05 Jun 2013 11:28:02 +0300")
Kalle Valo <kvalo@adurom.com> writes:
> "Arend van Spriel" <arend@broadcom.com> writes:
>
>> This patch fixes a regression introduced by:
>>
>> commit 6da3b6c48d79da96a36c2632053cf4f53bf48fb2
>> Author: Hauke Mehrtens <hauke@hauke-m.de>
>> Date: Sun Mar 24 01:45:52 2013 +0100
>>
>> brcmsmac: remove brcms_bss_cfg->associated
>>
>> The regression behaviour is described in:
>>
>> http://www.spinics.net/lists/linux-wireless/msg107474.html
>
> The link is not a very reliable reference, it can die anytime and
> there's no way to know what message it refers to. Stating the message id
> would better. And the best would be to copy the full text to the commit
> log, it's only few lines anyway.
Johannes gave a handy tip. Gmane has a service which uses message ids:
http://mid.gmane.org/5197DC4F.7030503@broadcom.com
If the link or service dies, one can find the email with the message id
visible from the link.
--
Kalle Valo
next prev parent reply other threads:[~2013-06-05 8:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 7:59 [PATCH] brcmsmac: disable power-save related functions Arend van Spriel
2013-06-05 8:28 ` Kalle Valo
2013-06-05 8:44 ` Kalle Valo [this message]
2013-06-05 8:46 ` Arend van Spriel
2013-06-05 11:07 ` Hauke Mehrtens
2013-06-05 11:09 ` Kalle Valo
2013-06-05 11:11 ` Antonio Quartulli
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=874ndd3q20.fsf@purkki.adurom.net \
--to=kvalo@adurom.com \
--cc=arend@broadcom.com \
--cc=davem@davemloft.net \
--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).