From: "Rafał Miłecki" <zajec5@gmail.com>
To: linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
"Michael Büsch" <mb@bu3sch.de>
Cc: b43-dev@lists.infradead.org, "Rafał Miłecki" <zajec5@gmail.com>
Subject: [PATCH V2 0/3] ssb/b43(legacy): clean dangling cores workarounds
Date: Wed, 11 May 2011 00:08:15 +0200 [thread overview]
Message-ID: <BANLkTinfMbkyh9kB+hsmka-JcWXAYEPynw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimecZ0uB4V_b-8F784Tnbkqo71ORA@mail.gmail.com>
W dniu 8 maja 2011 19:54 u?ytkownik Rafa? Mi?ecki <zajec5@gmail.com> napisa?:
> W dniu 8 maja 2011 20:30 u?ytkownik Rafa? Mi?ecki <zajec5@gmail.com> napisa?:
>> There is no perfect place for this workarounds, but keeping it in ssb sounds
>> more reasonable.
>
> Uups, I didn't save edition fixing this grammatical mistake. I'm lucky
> it won't be visible anywhere in git log :)
John: something went wrong there. You applied b43 and b43legacy
patches, but they should applied *after* ssb patch I don't see in your
tree.
I don't know how many people can be affected by this... Can not tell
you if we should rebase or just commit ssb patch quickly.
--
Rafa?
next prev parent reply other threads:[~2011-05-10 22:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-08 18:30 [PATCH V2 0/3] ssb/b43(legacy): clean dangling cores workarounds Rafał Miłecki
2011-05-08 17:54 ` Rafał Miłecki
2011-05-10 22:08 ` Rafał Miłecki [this message]
2011-05-10 22:30 ` Larry Finger
2011-05-11 17:12 ` John W. Linville
2011-05-08 18:30 ` [PATCH V2 1/3] ssb: update list of devices supporting multiple 80211 cores Rafał Miłecki
2011-05-08 18:30 ` [PATCH V2 2/3] b43: drop ssb-duplicated workaround for dangling cores Rafał Miłecki
2011-05-08 18:30 ` [PATCH V2 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=BANLkTinfMbkyh9kB+hsmka-JcWXAYEPynw@mail.gmail.com \
--to=zajec5@gmail.com \
--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).