From: Dvora Fuxbrumer <dvorax.fuxbrumer@linux.intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net-next v2 04/11] igb/igc: use strongly typed pointer
Date: Sun, 11 Apr 2021 10:09:37 +0300 [thread overview]
Message-ID: <e290e053-5118-1357-f4e5-6744be7fcc8e@linux.intel.com> (raw)
In-Reply-To: <20210326003834.3886241-5-jesse.brandeburg@intel.com>
On 26/03/2021 03:38, Jesse Brandeburg wrote:
> The igb and igc driver both use a trick of creating a local type
> pointer on the stack to ease dealing with a receive descriptor in
> 64 bit chunks for printing. Sparse however was not taken into
> account and receive descriptors are always in little endian
> order, so just make the unions use __le64 instead of u64.
>
> No functional change.
>
> Signed-off-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
> ---
> Warning Detail:
> CHECK .../igb/igb_main.c
> .../igb/igb_main.c:442:25: warning: cast to restricted __le64
> .../igb/igb_main.c:442:25: warning: cast to restricted __le64
> .../igb/igb_main.c:522:33: warning: cast to restricted __le64
> .../igb/igb_main.c:522:33: warning: cast to restricted __le64
> .../igb/igb_main.c:528:33: warning: cast to restricted __le64
> .../igb/igb_main.c:528:33: warning: cast to restricted __le64
> CHECK .../igc/igc_dump.c
> .../igc/igc_dump.c:192:40: warning: cast to restricted __le64
> .../igc/igc_dump.c:193:37: warning: cast to restricted __le64
> .../igc/igc_dump.c:275:45: warning: cast to restricted __le64
> .../igc/igc_dump.c:276:45: warning: cast to restricted __le64
> .../igc/igc_dump.c:281:45: warning: cast to restricted __le64
> .../igc/igc_dump.c:282:45: warning: cast to restricted __le64
> ---
> drivers/net/ethernet/intel/igb/igb_main.c | 2 +-
> drivers/net/ethernet/intel/igc/igc_dump.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
Tested for igc
Tested-by: Dvora Fuxbrumer <dvorax.fuxbrumer@linux.intel.com>
next prev parent reply other threads:[~2021-04-11 7:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 0:38 [Intel-wired-lan] [PATCH net-next v2 00/11] warning cleanups Jesse Brandeburg
2021-03-26 0:38 ` [Intel-wired-lan] [PATCH net-next v2 01/11] e100: handle eeprom as little endian Jesse Brandeburg
2021-03-26 0:38 ` [Intel-wired-lan] [PATCH net-next v2 02/11] intel: remove checker warning Jesse Brandeburg
2021-04-22 22:53 ` Switzer, David
2021-03-26 0:38 ` [Intel-wired-lan] [PATCH net-next v2 03/11] fm10k: move error check Jesse Brandeburg
2021-03-26 0:38 ` [Intel-wired-lan] [PATCH net-next v2 04/11] igb/igc: use strongly typed pointer Jesse Brandeburg
2021-04-11 7:09 ` Dvora Fuxbrumer [this message]
2021-04-22 22:06 ` Switzer, David
2021-04-22 23:11 ` Switzer, David
2021-03-26 0:38 ` [Intel-wired-lan] [PATCH net-next v2 05/11] igb: handle vlan types with checker enabled Jesse Brandeburg
2021-04-22 22:08 ` Switzer, David
2021-03-26 0:38 ` [Intel-wired-lan] [PATCH net-next v2 06/11] igb: fix assignment on big endian machines Jesse Brandeburg
2021-04-22 22:10 ` Switzer, David
2021-03-26 0:38 ` [Intel-wired-lan] [PATCH net-next v2 07/11] igb: override two checker warnings Jesse Brandeburg
2021-04-22 22:09 ` Switzer, David
2021-03-26 0:38 ` [Intel-wired-lan] [PATCH net-next v2 08/11] intel: call csum functions with well formatted arguments Jesse Brandeburg
2021-03-26 0:38 ` [Intel-wired-lan] [PATCH net-next v2 09/11] igbvf: convert to strongly typed descriptors Jesse Brandeburg
2021-03-26 0:38 ` [Intel-wired-lan] [PATCH net-next v2 10/11] ixgbe: use checker safe conversions Jesse Brandeburg
2021-04-23 22:38 ` Switzer, David
2021-03-26 0:38 ` [Intel-wired-lan] [PATCH net-next v2 11/11] ixgbe: reduce checker warnings Jesse Brandeburg
2021-03-26 1:32 ` Shannon Nelson
2021-04-23 22:39 ` Switzer, David
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=e290e053-5118-1357-f4e5-6744be7fcc8e@linux.intel.com \
--to=dvorax.fuxbrumer@linux.intel.com \
--cc=intel-wired-lan@osuosl.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