From: Vasu Dev <vasu.dev@linux.intel.com>
To: Vaishali Thakkar <vthakkar1994@gmail.com>
Cc: Vasu Dev <vasu.dev@intel.com>,
fcoe-devel@open-fcoe.org,
"James E.J. Bottomley" <JBottomley@odin.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [Open-FCoE] [PATCH] scsi: fcoe: Convert use of __constant_htons to htons
Date: Tue, 01 Sep 2015 15:43:24 -0700 [thread overview]
Message-ID: <1441147404.19451.52.camel@lin-nd1-054.jf.intel.com> (raw)
In-Reply-To: <20150819054844.GA21960@localhost>
On Wed, 2015-08-19 at 11:18 +0530, Vaishali Thakkar wrote:
> In little endian cases, the macro htons unfolds to __swab16 which
> provides special case for constants. In big endian cases,
> __constant_htons and htons expand directly to the same expression.
> So, replace __constant_htons with htons with the goal of getting
> rid of the definition of __constant_htons completely.
>
> The semantic patch that performs this transformation is as follows:
>
> @@expression x;@@
>
> - __constant_htons(x)
> + htons(x)
>
> Signed-off-by: Vaishali Thakkar <vthakkar1994@gmail.com>
> ---
> drivers/scsi/fcoe/fcoe.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/scsi/fcoe/fcoe.c b/drivers/scsi/fcoe/fcoe.c
> index ec193a8..d3eb80c 100644
> --- a/drivers/scsi/fcoe/fcoe.c
> +++ b/drivers/scsi/fcoe/fcoe.c
> @@ -364,7 +364,7 @@ static int fcoe_interface_setup(struct fcoe_interface *fcoe,
> * on the ethertype for the given device
> */
> fcoe->fcoe_packet_type.func = fcoe_rcv;
> - fcoe->fcoe_packet_type.type = __constant_htons(ETH_P_FCOE);
> + fcoe->fcoe_packet_type.type = htons(ETH_P_FCOE);
> fcoe->fcoe_packet_type.dev = netdev;
> dev_add_pack(&fcoe->fcoe_packet_type);
>
Acked-by: Vasu Dev <vasu.dev@intel.com>
prev parent reply other threads:[~2015-09-01 22:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 5:48 Vaishali Thakkar
2015-09-01 22:43 ` Vasu Dev [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=1441147404.19451.52.camel@lin-nd1-054.jf.intel.com \
--to=vasu.dev@linux.intel.com \
--cc=JBottomley@odin.com \
--cc=fcoe-devel@open-fcoe.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=vasu.dev@intel.com \
--cc=vthakkar1994@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
all inboxes | Powered by JetHome®