From: Jiri Slaby <jirislaby@gmail.com>
To: Sujith <Sujith.Manoharan@atheros.com>
Cc: Vasanth Thiagarajan <Vasanth.Thiagarajan@Atheros.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: useless ath9k commit logs
Date: Wed, 09 Dec 2009 13:05:33 +0100 [thread overview]
Message-ID: <4B1F928D.6050000@gmail.com> (raw)
In-Reply-To: <19231.35710.80659.717664@gargle.gargle.HOWL>
On 12/09/2009 12:35 PM, Sujith wrote:
> This is also a bug fix. Rate control gets bumpy when switching between
> APs operating in different modes. This was identified by internal testing.
>
> Hope this helps.
Ah, thanks, there are many of them though, these were just examples.
Please add such a description to each changelog from now on. I think
many kernel distro packagers will appreciate that.
thanks again,
--
js
prev parent reply other threads:[~2009-12-09 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 10:07 useless ath9k commit logs Jiri Slaby
2009-12-09 11:35 ` Sujith
2009-12-09 12:05 ` Jiri Slaby [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=4B1F928D.6050000@gmail.com \
--to=jirislaby@gmail.com \
--cc=Sujith.Manoharan@atheros.com \
--cc=Vasanth.Thiagarajan@Atheros.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).