From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Justin Tee <justintee8345@gmail.com>
Cc: linux-scsi@vger.kernel.org, jsmart2021@gmail.com,
justin.tee@broadcom.com, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH 1/1] lpfc: Fix incorrect big endian type assignments in FDMI and VMID paths
Date: Wed, 31 May 2023 18:18:21 -0400 [thread overview]
Message-ID: <yq11qiwcfh9.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20230530191405.21580-1-justintee8345@gmail.com> (Justin Tee's message of "Tue, 30 May 2023 12:14:05 -0700")
Justin,
> The kernel test robot reported sparse warnings regarding the improper
> usage of beXX_to_cpu macros.
>
> Change the flagged FDMI and VMID member variables to __beXX and redo
> the beXX_to_cpu macros appropriately.
Applied to 6.5/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2023-05-31 22:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 19:14 [PATCH 1/1] lpfc: Fix incorrect big endian type assignments in FDMI and VMID paths Justin Tee
2023-05-31 22:18 ` Martin K. Petersen [this message]
2023-06-08 1:42 ` Martin K. Petersen
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=yq11qiwcfh9.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=jsmart2021@gmail.com \
--cc=justin.tee@broadcom.com \
--cc=justintee8345@gmail.com \
--cc=linux-scsi@vger.kernel.org \
--cc=lkp@intel.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