All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Luciano Coelho <coelho@ti.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: pull request: wl12xx 2012-05-03
Date: Tue, 15 May 2012 18:01:05 -0400	[thread overview]
Message-ID: <20120515220105.GI24572@tuxdriver.com> (raw)
In-Reply-To: <1336050471.12189.37.camel@cumari.coelho.fi>

On Thu, May 03, 2012 at 04:07:51PM +0300, Luciano Coelho wrote:
> Hi John,
> 
> This is another pull request intended for 3.5.  A few fixes here and
> there, stuff that has been pending for a while and I hadn't had the time
> to apply.  Nothing really major.
> 
> Please pull or let me know if there's any problem. This tree is based on
> wireless-next/master and the head I want you to pull from is
> 422823e85d3957b64c573a2f15c6172d78de1e00. 
> 
> Thanks! 
> 
> The following changes since commit 0a9b3782ef402d27c3e6d1b116f10076a9dd088c:
> 
>   {nl,cfg,mac}80211: Allow user to see/configure HT protection mode (2012-05-02 14:30:55 -0400)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/luca/wl12xx.git for-linville
> 
> for you to fetch changes up to 422823e85d3957b64c573a2f15c6172d78de1e00:
> 
>   wlcore/wl12xx: implement better beacon loss handling (2012-05-03 15:45:03 +0300)

I used the magic of git to fix this up after last week's rebasing.
Please do take the opportunity to verify the result.

Thanks,

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2012-05-15 22:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-03 13:07 pull request: wl12xx 2012-05-03 Luciano Coelho
2012-05-15 22:01 ` John W. Linville [this message]
2012-05-16  3:08   ` Luciano Coelho

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=20120515220105.GI24572@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=coelho@ti.com \
    --cc=linux-wireless@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.