From: "Rafał Miłecki" <zajec5@gmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
"Michael Büsch" <mb@bu3sch.de>,
b43-dev@lists.infradead.org
Subject: [PATCH 0/3] ssb/b43(legacy): clean dangling cores workarounds
Date: Sun, 8 May 2011 19:11:44 +0200 [thread overview]
Message-ID: <BANLkTimNHB0mzAnndDeT9CsLKMTSYvLNGw@mail.gmail.com> (raw)
In-Reply-To: <4DC6CD8C.6080104@lwfinger.net>
2011/5/8 Larry Finger <Larry.Finger@lwfinger.net>:
> On 05/08/2011 12:09 PM, Rafa? Mi?ecki wrote:
>>
>> There is no perfect place for this workarounds, but keeping it in ssb
>> sounds
>> more reasonable.
>> 1) We already have in ssb similar workarounds for different cores
>> 2) We do not register not working devices in system
>> 3) We do not duplicate code in b43 and b43legacy
>>
>> Rafa? Mi?ecki (3):
>> ? ssb: update list of devices supporting multiple 80211 cores
>> ? b43: drop ssb-duplicated workaround for dangling cores
>> ? b43legacy: drop ssb-duplicated workaround for dangling cores
>>
>> ?drivers/net/wireless/b43/main.c ? ? ? | ? 17 -----------------
>> ?drivers/net/wireless/b43legacy/main.c | ? 18 ------------------
>> ?drivers/ssb/scan.c ? ? ? ? ? ? ? ? ? ?| ? ?5 ++++-
>> ?3 files changed, 4 insertions(+), 36 deletions(-)
>
> First of all, a minor grammatical mistake. It should be "this workaround" as
> there is only only one workaround discussed here.
>
> Secondly, "we do not register not working" is a little awkward. "We do not
> register inactive devices..." would be better.
>
> Finally, this commit message will never show up in the git commit logs. I
> think this info is valuable, thus it should be in the real commits.
>
> My suggestion for the [1/3] patch is something like:
>
> "Many of the BCM43xx chips contain cores that are attached to the SSB, but
> are inactive as they do not connect to the external environment. These must
> not be registered. Several of these types are handled in driver ssb;
> however, the specific case of an inactive 802.11 cores is now treated in b43
> and b43legacy. Although the current setup works, this minor change will
> place all such workarounds in ssb, and simplify the code in drivers b43 and
> b43legacy."
>
> In each of the other two patches, add a commit message something like:
>
> "Remove the code to detect inactive 802.11 cores, as that function is now
> done in ssb."
Thank you for reviewing.
> I have not yet tested the patches, but will do so soon.
Oh, do you have some device with 2 active cores? Nice :)
--
Rafa?
next prev parent reply other threads:[~2011-05-08 17:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-08 17:09 [PATCH 0/3] ssb/b43(legacy): clean dangling cores workarounds Rafał Miłecki
2011-05-08 17:06 ` Larry Finger
2011-05-08 17:11 ` Rafał Miłecki [this message]
2011-05-08 17:16 ` Michael Büsch
2011-05-08 18:34 ` Larry Finger
2011-05-08 18:36 ` Rafał Miłecki
2011-05-08 17:09 ` [PATCH 1/3] ssb: update list of devices supporting multiple 80211 cores Rafał Miłecki
2011-05-08 17:09 ` [PATCH 2/3] b43: drop ssb-duplicated workaround for dangling cores Rafał Miłecki
2011-05-08 17:09 ` [PATCH 3/3] b43legacy: " Rafał Miłecki
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=BANLkTimNHB0mzAnndDeT9CsLKMTSYvLNGw@mail.gmail.com \
--to=zajec5@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
/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).