From: "John W. Linville" <linville@tuxdriver.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-wireless@vger.kernel.org, b43-dev <b43-dev@lists.infradead.org>
Subject: Re: pull request: b43-next 2013-04-23
Date: Tue, 23 Apr 2013 14:10:44 -0400 [thread overview]
Message-ID: <20130423181044.GA7871@tuxdriver.com> (raw)
In-Reply-To: <CACna6rxOfr7jWKHfrGWC09Sw6XKShdexpkRKLeVhfuON5d7Bgw@mail.gmail.com>
On Tue, Apr 23, 2013 at 03:49:51PM +0200, Rafał Miłecki wrote:
> Hi John,
>
> Let me ask you once again for pulling my b43-next tree. I didn't add any new
> patches since the last pull request, I just dropped ssb patch you already
> pushed into your tree.
>
> Let me remind the changes for b43:
> > Changes include:
> > 1) Minor improvements for HT-PHY code (BCM4331)
> > 2) Code cleaning for HT-PHY and N-PHY
>
> Sorry for the problem with the previous pull request. Your wireless-next was
> slighlty too old for me (nouveau regression in 3.9-rc1) so I've based my tree
> on wireless-testing. That wasn't too bright idea.
>
> To rebase the tree I've simply used:
> git rebase --onto wireless-next/master master~21 master
>
>
> The following changes since commit c43933e61ea9b630521bf0d5cf06c155478308a7:
>
> mwifiex: remove redundant initialization for bss_descriptor
> (2013-04-22 15:38:36 -0400)
>
> are available in the git repository at:
>
> git://git.infradead.org/users/rafal/b43-next.git master
>
> for you to fetch changes up to 0c201cfbfd47c40ee0cedbcd96e4fbaa85c5fc50:
>
> b43: N-PHY: don't use deprecated b43_radio_foo16 (2013-04-23 12:27:58 +0200)
Pulling now...
--
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:[~2013-04-23 18:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 13:49 pull request: b43-next 2013-04-23 Rafał Miłecki
2013-04-23 18:10 ` 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=20130423181044.GA7871@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=b43-dev@lists.infradead.org \
--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).