From: Dan Williams <dcbw@redhat.com>
To: "Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>,
Matthias Kaehlcke <mka@chromium.org>
Cc: linux-wimax <linux-wimax@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Behan Webster <behanw@converseincode.com>,
Mark Charlebois <charlebm@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
Guenter Roeck <groeck@chromium.org>
Subject: Re: [PATCH] wimax/i2400m: Remove VLAIS
Date: Wed, 25 Oct 2017 12:39:00 -0500 [thread overview]
Message-ID: <1508953140.23414.1.camel@redhat.com> (raw)
In-Reply-To: <3A78FAA0EC814D4B8ECC99B3AB32B332843BB118@fmsmsx104.amr.corp.intel.com>
On Wed, 2017-10-25 at 17:12 +0000, Perez-Gonzalez, Inaky wrote:
> > On Tue, 2017-10-24 at 21:00 +0000, Perez-Gonzalez, Inaky wrote:
> > > > ping any comments on this?
> > >
> > > None from me; I don't have access to this HW anymore, so I can't
> > > validate if the change would work or not.
> > I still have a 5350 around somewhere, I can make sure firmware
> > loads if
> > you like.
>
> That'd be swell Dan, thx
Seems to load firmware, read the MAC, and reboot the card. Couldn't
get userspace tools working in a 5m try but the kernel module debug
traces indicate the card TX/RX-es commands and we can pull out the card
state and rfkill status and things like that.
Inaky, is that enough to verify the patch is OK?
Dan
next prev parent reply other threads:[~2017-10-25 17:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 19:41 [PATCH] wimax/i2400m: Remove VLAIS Matthias Kaehlcke
2017-10-24 19:46 ` Matthias Kaehlcke
2017-10-24 21:00 ` Perez-Gonzalez, Inaky
2017-10-25 15:57 ` Dan Williams
2017-10-25 17:12 ` Perez-Gonzalez, Inaky
2017-10-25 17:39 ` Dan Williams [this message]
2017-10-25 21:06 ` Perez-Gonzalez, Inaky
2017-10-25 21:01 ` Arnd Bergmann
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=1508953140.23414.1.camel@redhat.com \
--to=dcbw@redhat.com \
--cc=arnd@arndb.de \
--cc=behanw@converseincode.com \
--cc=charlebm@gmail.com \
--cc=groeck@chromium.org \
--cc=inaky.perez-gonzalez@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wimax@intel.com \
--cc=mka@chromium.org \
--cc=netdev@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 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).