linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antonio Quartulli <ordex@autistici.org>
To: Kalle Valo <kvalo@adurom.com>
Cc: Arend van Spriel <arend@broadcom.com>,
	"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, 5 Jun 2013 13:11:17 +0200	[thread overview]
Message-ID: <20130605111117.GD1789@ritirata.org> (raw)
In-Reply-To: <87zjv43jb8.fsf@purkki.adurom.net>

[-- Attachment #1: Type: text/plain, Size: 2008 bytes --]

On Wed, Jun 05, 2013 at 02:09:47PM +0300, Kalle Valo wrote:
> "Arend van Spriel" <arend@broadcom.com> writes:
> 
> > On 06/05/2013 10:44 AM, Kalle Valo wrote:
> >> 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.
> >>
> >
> > What if gmane dies ;-)
> 
> You missed my point. If gmane dies you do this:
> 
> http://lmgtfy.com/?q=5197DC4F.7030503%40broadcom.com
> 
> :D
> 
> The id above is the real message id from the email, that's why you can
> use it to search from email archives, google and so on.

Would it be too hard to copy the text in the commit message? :-)

Why should somebody jump here and there just to get the description of a bug?
Imho, at least a short description should appear here. In this way also David
can immediately figure out what the problem is, without jumping on the web
(imagine many of this in one pull request) :-)


my 2 cents.

Cheers,


-- 
Antonio Quartulli

..each of us alone is worth nothing..
Ernesto "Che" Guevara

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2013-06-05 11:13 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
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 [this message]

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=20130605111117.GD1789@ritirata.org \
    --to=ordex@autistici.org \
    --cc=arend@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=kvalo@adurom.com \
    --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).