From: Kalle Valo <kvalo@codeaurora.org>
To: Ganapathi Bhat <gbhat@marvell.com>
Cc: <linux-wireless@vger.kernel.org>,
Amitkumar Karwar <akarwar@marvell.com>,
Nishant Sarmukadam <nishants@marvell.com>,
Karthik Ananthapadmanabha <karthida@marvell.com>,
Ganapathi Bhat <gbhat@marvell.com>
Subject: Re: [v2,1/3] mwifiex: add qualifier to firmware structures
Date: Mon, 20 Mar 2017 17:06:03 +0000 (UTC) [thread overview]
Message-ID: <20170320170603.3373460854@smtp.codeaurora.org> (raw)
In-Reply-To: <1489048577-11293-2-git-send-email-gbhat@marvell.com>
Ganapathi Bhat <gbhat@marvell.com> wrote:
> From: Karthik Ananthapadmanabha <karthida@marvell.com>
>
> Adding qualifier "__packed" indicates that no padding should be
> performed on the qualified object for alignment.
> This patch adds qualifier __packed to the required firmware
> structures in mwifiex driver.
>
> Signed-off-by: Karthik Ananthapadmanabha <karthida@marvell.com>
> Signed-off-by: Ganapathi Bhat <gbhat@marvell.com>
3 patches applied to wireless-drivers-next.git, thanks.
5c0b87987432 mwifiex: add qualifier to firmware structures
5653c6462f56 mwifiex: Use accessors routines for unaligned values
92c70a958b0b mwifiex: fix for unaligned reads
--
https://patchwork.kernel.org/patch/9612875/
Documentation about submitting wireless patches and checking status
from patchwork:
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2017-03-20 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 8:36 [PATCH v2 0/3] mwifiex: Unaligned access fixes Ganapathi Bhat
2017-03-09 8:36 ` [PATCH v2 1/3] mwifiex: add qualifier to firmware structures Ganapathi Bhat
2017-03-20 17:06 ` Kalle Valo [this message]
2017-03-09 8:36 ` [PATCH v2 2/3] mwifiex: Use accessors routines for unaligned values Ganapathi Bhat
2017-03-09 8:36 ` [PATCH v2 3/3] mwifiex: fix for unaligned reads Ganapathi Bhat
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=20170320170603.3373460854@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=akarwar@marvell.com \
--cc=gbhat@marvell.com \
--cc=karthida@marvell.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nishants@marvell.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).