From: Jason Litzinger <jlitzingerdev@gmail.com>
To: aditya.shankar@microchip.com, ganesh.krishna@microchip.com,
gregkh@linuxfoundation.org
Cc: linux-wireless@vger.kernel.org, devel@driverdev.osuosl.org,
dan.carpenter@oracle.com
Subject: Re: [PATCH RFC] staging: wilc1000: Refactor handling of HT caps fields
Date: Tue, 25 Apr 2017 22:54:16 -0600 [thread overview]
Message-ID: <20170426045416.GA20613@arch-tinker.localdomain> (raw)
In-Reply-To: <20170426044625.20529-1-jlitzingerdev@gmail.com>
> + strStaParams.ht_capa = *params->ht_capa;
Doh, that's completely wrong. I had a few iterations of this and sent
the wrong version. There's an embedded array in that struct (not an
embedded struct as I though during one read through).
Will fix and re-send, sorry for the spam.
-Jason
next prev parent reply other threads:[~2017-04-26 4:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 4:46 [PATCH RFC] staging: wilc1000: Refactor handling of HT caps fields Jason Litzinger
2017-04-26 4:54 ` Jason Litzinger [this message]
2017-04-26 5:24 ` Jason Litzinger
2017-04-26 8:27 ` Dan Carpenter
2017-04-28 9:58 ` Greg KH
2017-04-28 16:11 ` Jason Litzinger
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=20170426045416.GA20613@arch-tinker.localdomain \
--to=jlitzingerdev@gmail.com \
--cc=aditya.shankar@microchip.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=ganesh.krishna@microchip.com \
--cc=gregkh@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox