All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Malcolm Priestley <tvboxspy@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/6] staging: vt6655: set_channel replace parameter with ieee80211_channel
Date: Mon, 12 Jan 2015 19:32:19 -0800	[thread overview]
Message-ID: <20150113033219.GA31093@kroah.com> (raw)
In-Reply-To: <54920EDC.4090007@gmail.com>

On Wed, Dec 17, 2014 at 11:16:44PM +0000, Malcolm Priestley wrote:
> 
> 
> On 04/12/14 22:12, Malcolm Priestley wrote:
> >replacing uConnectionChannel for hw_value as set in vnt_init_bands.
> >
> >This allows other signaling of ieee80211_channel to move deeper into
> >driver.
> >
> >Signed-off-by: Malcolm Priestley <tvboxspy@gmail.com>
> >---
> Hi greg
> 
> Can you drop this patch series altogether.
> 
> I will repost these later after some needed bug fixes for 3.19

Now dropped.

  reply	other threads:[~2015-01-13  5:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-04 22:12 [PATCH 1/6] staging: vt6655: set_channel replace parameter with ieee80211_channel Malcolm Priestley
2014-12-04 22:12 ` [PATCH 2/6] staging: vt6655: common variable size channel numbers to ieee80211_channel->hw_value Malcolm Priestley
2014-12-04 22:12 ` [PATCH 3/6] staging: vt6655: remove antenna diversity functions Malcolm Priestley
2014-12-04 22:12 ` [PATCH 4/6] staging: vt6655: device_init_registers alway set initial antenna mode Malcolm Priestley
2014-12-04 22:12 ` [PATCH 5/6] staging: vt6655: Fix RFbSetPower() error: buffer overflow 'priv->abyCCKPwrTbl' 15 <= 56 Malcolm Priestley
2014-12-04 22:12 ` [PATCH 6/6] staging: vt6655: RFbSetPower remove unused variable byPwrdBm Malcolm Priestley
2014-12-17 23:16 ` [PATCH 1/6] staging: vt6655: set_channel replace parameter with ieee80211_channel Malcolm Priestley
2015-01-13  3:32   ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-01-19 18:24 Malcolm Priestley

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=20150113033219.GA31093@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tvboxspy@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 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.