linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Naveen Singh <nsingh@atheros.com>
Cc: "greg@kroah.com" <greg@kroah.com>,
	"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Vipin Mehta <Vipin.Mehta@Atheros.com>,
	"Luis Rodriguez" <Luis.Rodriguez@Atheros.com>,
	Naveen Singh <Naveen.Singh@Atheros.com>,
	Kalle Valo <kalle.valo@atheros.com>
Subject: Re: [PATCH 0/5] staging:ath6kl:patches for supporting 2.1.1 and bug fixes
Date: Thu, 21 Apr 2011 12:01:56 -0700	[thread overview]
Message-ID: <20110421190156.GG8399@tux> (raw)
In-Reply-To: <1302148341-1783-1-git-send-email-nsingh@atheros.cm>

On Wed, Apr 06, 2011 at 08:52:16PM -0700, Naveen Singh wrote:
> From: Naveen Singh <nsingh@atheros.com>
> 
> Greg,
> 
> These are set of 5 patches for ath6kl. These patches are related
> to the correct functionality of driver as well as providing the
> support of 2.1.1 silicon in the upstream driver.
> 
> I have tested each and every patch.With each and every patch I was
> able to compile the kernel, load the kernel, and do a basic connectivity
> test with an external AP.These patches are tested on wireless-testing
> as compared to staging-next because top of staging-next compilation
> was broken. To do this I applied all the patches related to ath6k from 
> staging-next tree to the wireless-testing tree and then I applied these
> patches.
> 
> These should apply cleanly to staging-next tree as well. Let me know if
> you have any issues.
> 
> Naveen Singh (5):
>   staging:at6kl:Support for V2.1.1 Silicon
>   staging:ath6kl: Introduction of new CMD/EVT ID
>   staging:ath6kl:DEV ID in the DATA/CMD Packet
>   staging:ath6kl:Scan operation while disconnect
>   staging:ath6kl:cfg ops for power management

Greg, don't even bother with this series, it no longer applies, we will resend
a new one that applies cleanly to the tree.

  Luis

      parent reply	other threads:[~2011-04-21 19:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1302148341-1783-1-git-send-email-nsingh@atheros.cm>
2011-04-12 20:28 ` [PATCH 0/5] staging:ath6kl:patches for supporting 2.1.1 and bug fixes Vipin Mehta
2011-04-21  1:11   ` Luis R. Rodriguez
2011-04-21  1:22     ` Greg KH
2011-04-21 19:01 ` Luis R. Rodriguez [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=20110421190156.GG8399@tux \
    --to=lrodriguez@atheros.com \
    --cc=Luis.Rodriguez@Atheros.com \
    --cc=Naveen.Singh@Atheros.com \
    --cc=Vipin.Mehta@Atheros.com \
    --cc=devel@linuxdriverproject.org \
    --cc=greg@kroah.com \
    --cc=kalle.valo@atheros.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nsingh@atheros.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).