Linux wireless drivers development
 help / color / mirror / Atom feed
From: Jacob Kiefer <jtk54@cornell.edu>
To: Jes Sorensen <Jes.Sorensen@redhat.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Rickard Strandqvist <rickard_strandqvist@spectrumdigital.se>,
	Roberta Dobrescu <roberta.dobrescu@gmail.com>,
	"Gujulan Elango, Hari Prasath (H.)" <hgujulan@visteon.com>,
	"open list:STAGING - REALTEK RTL8723U WIRELESS DRIVER"
	<linux-wireless@vger.kernel.org>,
	"open list:STAGING SUBSYSTEM" <devel@driverdev.osuosl.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2 v3] drivers: staging: rtl8723au: Changed rssi_cmd to little-endian param
Date: Sun, 18 Oct 2015 15:11:56 -0400	[thread overview]
Message-ID: <20151018191154.GA2936@jtk54-Q550LF> (raw)
In-Reply-To: <wrfj612ewi7d.fsf@redhat.com>

> I am fine with this code in principle, but has it been tested? This
> stuff will break the driver miserably if it's wrong.
> 
> Thanks,
> Jes
> 

This patchset has not been tested.
Unfortunately, I don't have to proper card to test this patch on my
local. It built for me, and that's as far as I went.

Is there a way for me to test this patch locally _without_ the
corresponding wireless card? I will gladly do this, I just need to know
the tools to use and methodology.

Otherwise, can anyone with the correct wireless card apply these patches to a copy of the kernel and
test that nothing breaks because of the patch on their machine? Again
this is for the RTL8723au wireless card.

Thanks,
Jake

      reply	other threads:[~2015-10-18 19:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-10 19:28 [PATCH 1/2 v3] drivers: staging: rtl8723au: Changed rssi_cmd to little-endian param Jacob Kiefer
2015-10-10 19:28 ` [PATCH 2/2 v3] drivers: staging: rtl8723au: Changed raid_cmd to little-endian mask Jacob Kiefer
2015-10-10 21:02 ` [PATCH 1/2 v3] drivers: staging: rtl8723au: Changed rssi_cmd to little-endian param Jes Sorensen
2015-10-18 19:11   ` Jacob Kiefer [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=20151018191154.GA2936@jtk54-Q550LF \
    --to=jtk54@cornell.edu \
    --cc=Jes.Sorensen@redhat.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hgujulan@visteon.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rickard_strandqvist@spectrumdigital.se \
    --cc=roberta.dobrescu@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