[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5687E8DB.3080706@users.sourceforge.net>
Date: Sat, 2 Jan 2016 16:12:27 +0100
From: SF Markus Elfring <elfring@...rs.sourceforge.net>
To: linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
Kalle Valo <kvalo@...eaurora.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org,
Julia Lawall <julia.lawall@...6.fr>
Subject: net-rsi: Reconsider usage of variable "vap_id" in rsi_send_mgmt_pkt()
Hello,
I have taken another look at the implementation of the function "rsi_send_mgmt_pkt".
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/tree/drivers/net/wireless/rsi/rsi_91x_pkt.c?id=e8c58e7a5a106c3d557fccd01cd4d1128f9bab38#n114
I find the following statement combination interesting there.
…
u8 vap_id = 0;
…
msg[7] |= cpu_to_le16(vap_id << 8);
…
I would appreciate a further clarification.
Does a shift operation for a variable which contains zero indicate an open issue?
Regards,
Markus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists