From: John W. Linville <linville@tuxdriver.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH] ath9k: Re-enable interrupts after a channel change failure
Date: Mon, 1 Apr 2013 13:43:43 -0400 [thread overview]
Message-ID: <20130401174343.GE21859@tuxdriver.com> (raw)
In-Reply-To: <CAJ-Vmo=TBiJjs-DF-BfV95Mz8-Ro_aDa-dxcSOVC20rk9T5bqA@mail.gmail.com>
On Mon, Apr 01, 2013 at 09:25:43AM -0700, Adrian Chadd wrote:
> You filed a bug against this, right? Can you mention the bug report in there?
>
> (What's the "blessed" way to mention a bugzilla.kernel.org bug in a
> linux git commit?)
I usually just include the URL. "Fixes Bug #12345" would suffice as well.
--
John W. Linville Someday the world will need a hero, and you
linville at tuxdriver.com might be all we have. Be ready.
WARNING: multiple messages have this Message-ID (diff)
From: "John W. Linville" <linville@tuxdriver.com>
To: Adrian Chadd <adrian@freebsd.org>
Cc: Robert Shade <robert.shade@gmail.com>,
linux-wireless@vger.kernel.org, ath9k-devel@venema.h4ckr.net
Subject: Re: [PATCH] ath9k: Re-enable interrupts after a channel change failure
Date: Mon, 1 Apr 2013 13:43:43 -0400 [thread overview]
Message-ID: <20130401174343.GE21859@tuxdriver.com> (raw)
In-Reply-To: <CAJ-Vmo=TBiJjs-DF-BfV95Mz8-Ro_aDa-dxcSOVC20rk9T5bqA@mail.gmail.com>
On Mon, Apr 01, 2013 at 09:25:43AM -0700, Adrian Chadd wrote:
> You filed a bug against this, right? Can you mention the bug report in there?
>
> (What's the "blessed" way to mention a bugzilla.kernel.org bug in a
> linux git commit?)
I usually just include the URL. "Fixes Bug #12345" would suffice as well.
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2013-04-01 17:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-01 14:22 [ath9k-devel] [PATCH] ath9k: Re-enable interrupts after a channel change failure Robert Shade
2013-04-01 14:22 ` Robert Shade
2013-04-01 16:25 ` [ath9k-devel] " Adrian Chadd
2013-04-01 16:25 ` Adrian Chadd
2013-04-01 16:53 ` [ath9k-devel] " Robert Shade
2013-04-01 17:43 ` John W. Linville [this message]
2013-04-01 17:43 ` John W. Linville
2013-04-01 17:40 ` [ath9k-devel] " Felix Fietkau
2013-04-01 17:40 ` Felix Fietkau
2013-04-02 12:03 ` [ath9k-devel] " Robert Shade
2013-04-02 12:03 ` Robert Shade
2013-04-02 12:24 ` [ath9k-devel] " Felix Fietkau
2013-04-02 12:24 ` Felix Fietkau
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=20130401174343.GE21859@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=ath9k-devel@lists.ath9k.org \
/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.