linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Prasun Maiti <prasunmaiti87@gmail.com>
Cc: Amitkumar Karwar <akarwar@marvell.com>,
	Nishant Sarmukadam <nishants@marvell.com>,
	Linux Wireless <linux-wireless@vger.kernel.org>,
	Linux Next <linux-next@vger.kernel.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [v4] mwifiex: Reduce endian conversion for REG Host Commands
Date: Mon, 18 Jul 2016 19:33:14 +0000 (UTC)	[thread overview]
Message-ID: <20160718193314.3B9A26043B@smtp.codeaurora.org> (raw)
In-Reply-To: <1467022402-23990-1-git-send-email-prasunmaiti87@gmail.com>

Prasun Maiti <prasunmaiti87@gmail.com> wrote:
> For multiple REG Host Commands (e.g HostCmd_CMD_802_11_EEPROM_ACCESS,
> HostCmd_CMD_MAC_REG_ACCESS etc.) "cpu_to_leX"-converted values are
> saved to driver. So, "leX_to_cpu" conversion is required too many
> times afterwards in driver.
> 
> This patch reduces the endian: conversion without saving "cpu_to_leX"
> converted values in driver. This will convert endianness in prepare
> command and command response path.
> 
> Signed-off-by: Prasun Maiti <prasunmaiti87@gmail.com>
> Acked-by: Amitkumar Karwar <akarwar@marvell.com>

Thanks, 1 patch applied to wireless-drivers-next.git:

8cfb86003dbf mwifiex: Reduce endian conversion for REG Host Commands

-- 
Sent by pwcli
https://patchwork.kernel.org/patch/9200265/

      parent reply	other threads:[~2016-07-18 19:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-23  5:29 [PATCH v3] mwifiex: Reduce endian conversion for REG Host Commands Prasun Maiti
2016-06-27  7:02 ` Amitkumar Karwar
2016-06-27 10:13   ` [PATCH v4] " Prasun Maiti
2016-07-08 11:02     ` Amitkumar Karwar
2016-07-08 13:40       ` Kalle Valo
2016-07-08 14:32         ` Amitkumar Karwar
2016-07-08 14:33     ` Amitkumar Karwar
2016-07-18 19:33     ` Kalle Valo [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=20160718193314.3B9A26043B@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=akarwar@marvell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nishants@marvell.com \
    --cc=prasunmaiti87@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;
as well as URLs for NNTP newsgroup(s).