From: "Franky Lin" <frankyl@broadcom.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 0/7] miscellaneous fixes intended for 3.7
Date: Mon, 15 Oct 2012 12:06:46 -0700 [thread overview]
Message-ID: <507C5EC6.6000306@broadcom.com> (raw)
In-Reply-To: <20121015182756.GE16817@tuxdriver.com>
On 10/15/2012 11:27 AM, John W. Linville wrote:
> On Wed, Oct 10, 2012 at 11:13:05AM -0700, Franky Lin wrote:
>> Here are some miscellaneous brcmfmac bug fix patches aiming for 3.7
>>
>> Arend van Spriel (1):
>> brcmfmac: remove 'always false' condition from brcmf_c_mkiovar_bsscfg
>>
>> Dan Carpenter (2):
>> brcmfmac: Using zero instead of NULL
>>
>> Franky Lin (3):
>> brcmfmac: fix sparse warnings
>
> These don't strike me as meaningful bug fixes. I'll hold them for 3.8.
>
> John
>
OK, thanks John.
Franky
prev parent reply other threads:[~2012-10-15 19:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 18:13 [PATCH 0/7] miscellaneous fixes intended for 3.7 Franky Lin
2012-10-10 18:13 ` [PATCH 1/7] brcmfmac: handle all exceptions as an error Franky Lin
2012-10-10 18:13 ` [PATCH 2/7] brcmfmac: Using zero instead of NULL Franky Lin
2012-10-10 18:13 ` [PATCH 3/7] brcmfmac: fix sparse warnings Franky Lin
2012-10-10 18:13 ` [PATCH 4/7] brcmfmac: use control channel in roamed status reporting Franky Lin
2012-10-10 18:13 ` [PATCH 5/7] brcmfmac: set dongle mode accordingly when interface up Franky Lin
2012-10-10 18:13 ` [PATCH 6/7] brcmfmac: remove 'always false' condition from brcmf_c_mkiovar_bsscfg Franky Lin
2012-10-10 18:13 ` [PATCH 7/7] brcmfmac: fix end of loop check (signedness bug) Franky Lin
2012-10-15 18:27 ` [PATCH 0/7] miscellaneous fixes intended for 3.7 John W. Linville
2012-10-15 19:06 ` Franky Lin [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=507C5EC6.6000306@broadcom.com \
--to=frankyl@broadcom.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).