linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: alobakin@marvell.com
Cc: kuba@kernel.org, irusskikh@marvell.com,
	michal.kalderon@marvell.com, aelior@marvell.com,
	denis.bolotin@marvell.com, GR-everest-linux-l2@marvell.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/9] net: qed/qede: W=1 C=1 warnings cleanup
Date: Mon, 06 Jul 2020 13:19:10 -0700 (PDT)	[thread overview]
Message-ID: <20200706.131910.1401749404818988951.davem@davemloft.net> (raw)
In-Reply-To: <20200706153821.786-1-alobakin@marvell.com>

From: Alexander Lobakin <alobakin@marvell.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.

      parent reply	other threads:[~2020-07-06 20:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-06 15:38 [PATCH net-next 0/9] net: qed/qede: W=1 C=1 warnings cleanup Alexander Lobakin
2020-07-06 15:38 ` [PATCH net-next 1/9] net: qed: move static iro_arr[] out of header file Alexander Lobakin
2020-07-06 15:38 ` [PATCH net-next 2/9] net: qed: cleanup global structs declarations Alexander Lobakin
2020-07-06 15:38 ` [PATCH net-next 3/9] net: qed: correct qed_hw_err_notify() prototype Alexander Lobakin
2020-07-06 15:38 ` [PATCH net-next 4/9] net: qed: address kernel-doc warnings Alexander Lobakin
2020-07-06 15:38 ` [PATCH net-next 5/9] net: qed: improve indentation of some parts of code Alexander Lobakin
2020-07-06 15:38 ` [PATCH net-next 6/9] net: qed: use ptr shortcuts to dedup field accessing in some parts Alexander Lobakin
2020-07-06 15:38 ` [PATCH net-next 7/9] net: qed: sanitize BE/LE data processing Alexander Lobakin
2020-07-06 15:38 ` [PATCH net-next 8/9] net: qede: fix kernel-doc for qede_ptp_adjfreq() Alexander Lobakin
2020-07-06 15:38 ` [PATCH net-next 9/9] net: qede: fix BE vs CPU comparison Alexander Lobakin
2020-07-06 20:19 ` David Miller [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=20200706.131910.1401749404818988951.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=GR-everest-linux-l2@marvell.com \
    --cc=aelior@marvell.com \
    --cc=alobakin@marvell.com \
    --cc=denis.bolotin@marvell.com \
    --cc=irusskikh@marvell.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.kalderon@marvell.com \
    --cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).