From: "John W. Linville" <linville@tuxdriver.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 0/3] b43: Is this series still valid??
Date: Wed, 22 Dec 2010 15:02:15 -0500 [thread overview]
Message-ID: <20101222200215.GE10046@tuxdriver.com> (raw)
In-Reply-To: <AANLkTikJcCWph2OCp+eaEsdKDXT8Q374KFp=13zX+Rro@mail.gmail.com>
On Wed, Dec 22, 2010 at 08:20:18PM +0100, Rafał Miłecki wrote:
> 2010/12/22 John W. Linville <linville@tuxdriver.com>:
> > I found this old series pending in my queue from months ago. I sat on
> > them because they had some discussion and never got reposted.
> >
> > Looking closer, the discussion never amounted to a NAK. So, I tried
> > applying them, and they applied with only minor massaging.
> >
> > So, are these still valid?
> >
> > Let me know...
>
> The way we call init in one of patches may be incorrect, I'm not sure
> if we still need to keep b_width (from other patch). I think it'll be
> better to ignore that patches for now.
OK, I'll drop them -- please repost if/when they are ready...
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2010-12-22 20:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 19:11 [PATCH 0/3] b43: Is this series still valid?? John W. Linville
2010-12-22 19:11 ` [PATCH 1/3] b43: N-PHY: band width setting with dumb clock control call John W. Linville
2010-12-22 19:11 ` [PATCH 2/3] b43: N-PHY: add sub calls of band width setting John W. Linville
2010-12-22 19:11 ` [PATCH 3/3] b43: N-PHY: check for clk when setting RX core state John W. Linville
2010-12-22 19:20 ` [PATCH 0/3] b43: Is this series still valid?? Rafał Miłecki
2010-12-22 20:02 ` John W. Linville [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=20101222200215.GE10046@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@vger.kernel.org \
--cc=zajec5@gmail.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).