From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: linux1394-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] Revert "firewire: ohci: use common macro to interpret be32 data in le32 buffer"
Date: Mon, 8 Jul 2024 06:43:26 +0900 [thread overview]
Message-ID: <20240707214326.GA16237@workstation.local> (raw)
In-Reply-To: <20240707134523.11784-1-o-takashi@sakamocchi.jp>
On Sun, Jul 07, 2024 at 10:45:23PM +0900, Takashi Sakamoto wrote:
> This reverts commit f26a38e61c03fdfacb6b596e1daf665cf4526a60, since it
> causes the following sparse warnings:
>
> sparse warnings: (new ones prefixed by >>)
> >> drivers/firewire/ohci.c:891:23: sparse: sparse: cast to restricted __be32
> >> drivers/firewire/ohci.c:891:23: sparse: sparse: cast from restricted __le32
> drivers/firewire/ohci.c:892:23: sparse: sparse: cast to restricted __be32
> drivers/firewire/ohci.c:892:23: sparse: sparse: cast from restricted __le32
> drivers/firewire/ohci.c:893:23: sparse: sparse: cast to restricted __be32
> drivers/firewire/ohci.c:893:23: sparse: sparse: cast from restricted __le32
> drivers/firewire/ohci.c:905:31: sparse: sparse: cast to restricted __be32
> drivers/firewire/ohci.c:905:31: sparse: sparse: cast from restricted __le32
> drivers/firewire/ohci.c:914:31: sparse: sparse: cast to restricted __be32
> drivers/firewire/ohci.c:914:31: sparse: sparse: cast from restricted __le32
> drivers/firewire/ohci.c:939:18: sparse: sparse: cast to restricted __be32
> drivers/firewire/ohci.c:939:18: sparse: sparse: cast from restricted __le32
> drivers/firewire/ohci.c:2033:23: sparse: sparse: cast to restricted __be32
> drivers/firewire/ohci.c:2033:23: sparse: sparse: cast from restricted __le32
> drivers/firewire/ohci.c:2037:27: sparse: sparse: cast to restricted __be32
> drivers/firewire/ohci.c:2037:27: sparse: sparse: cast from restricted __le32
> drivers/firewire/ohci.c:2038:27: sparse: sparse: cast to restricted __be32
> drivers/firewire/ohci.c:2038:27: sparse: sparse: cast from restricted __le32
>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202407050656.03bw1YXA-lkp@intel.com/
> Signed-off-by: Takashi Sakamoto <o-takashi@sakamocchi.jp>
> ---
> drivers/firewire/ohci.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied to for-next branch.
Regards
Takashi Sakamoto
prev parent reply other threads:[~2024-07-07 21:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-07 13:45 [PATCH] Revert "firewire: ohci: use common macro to interpret be32 data in le32 buffer" Takashi Sakamoto
2024-07-07 21:43 ` Takashi Sakamoto [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=20240707214326.GA16237@workstation.local \
--to=o-takashi@sakamocchi.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--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