netdev - Re: [PATCH net-next 0/9] net: qed/qede: W=1 C=1 warnings cleanup

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20200706.131910.1401749404818988951.davem@davemloft.net>
Date:   Mon, 06 Jul 2020 13:19:10 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     alobakin@...vell.com
Cc:     kuba@...nel.org, irusskikh@...vell.com,
        michal.kalderon@...vell.com, aelior@...vell.com,
        denis.bolotin@...vell.com, GR-everest-linux-l2@...vell.com,
        netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next 0/9] net: qed/qede: W=1 C=1 warnings cleanup

From: Alexander Lobakin <alobakin@...vell.com>
Date: Mon, 6 Jul 2020 18:38:12 +0300

> This set cleans qed/qede build log under W=1 C=1 with GCC 8 and
> sparse 0.6.2. The only thing left is "context imbalance -- unexpected
> unlock" in one of the source files, which will be issued later during
> the refactoring cycles.
> 
> The biggest part is handling the endianness warnings. The current code
> often just assumes that both host and device operate in LE, which is
> obviously incorrect (despite the fact that it's true for x86 platforms),
> and makes sparse {s,m}ad.
> 
> The rest of the series is mostly random non-functional fixes
> here-and-there.

Series applied, thank you.