netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: Yuval.Mintz@cavium.com
Cc: netdev@vger.kernel.org, Manish.Chopra@cavium.com
Subject: Re: [PATCH net-next 01/11] qede: Fix sparse warnings
Date: Mon, 22 May 2017 14:29:03 -0400 (EDT)	[thread overview]
Message-ID: <20170522.142903.2151382146475588141.davem@davemloft.net> (raw)
In-Reply-To: <BLUPR0701MB20043F202421D02E697198338DF80@BLUPR0701MB2004.namprd07.prod.outlook.com>

From: "Mintz, Yuval" <Yuval.Mintz@cavium.com>
Date: Mon, 22 May 2017 17:44:12 +0000

>> >> Please.
>> >> 
>> >> This is exactly the problem when such a terse commit message, or lack of any
>> >> message at all as is the case here, occurs.
>> >> 
>> >> I have no idea what removing this method assignment has to do with fixing
>> >> sparse warnings.
>> > 
>> > It's currently defined twice in the qede_dcbnl_ops struct -
> 
>> >Ok, so what's important is that you don't just post a patch with no
>> commit message, just saying "sparse warning fixes."
> 
>> At a minimum, if you're too lazy to explain what exactly each thing
>> is fixing, provide the sparse warnings you are eliminating in the
>> commit message.
> 
> Well, this time it was intentional lazines; Thought it would have been
> wasted reading. But sure, here it is:
> 
> drivers/net/ethernet/qlogic/qede/qede_fp.c:349:34: warning: invalid assignment: |=
> drivers/net/ethernet/qlogic/qede/qede_fp.c:349:34:    left side has type restricted __le16
> drivers/net/ethernet/qlogic/qede/qede_fp.c:349:34:    right side has type int
> drivers/net/ethernet/qlogic/qede/qede_fp.c:1516:50: warning: invalid assignment: |=
> drivers/net/ethernet/qlogic/qede/qede_fp.c:1516:50:    left side has type restricted __le16
> drivers/net/ethernet/qlogic/qede/qede_fp.c:1516:50:    right side has type int
> drivers/net/ethernet/qlogic/qede/qede_fp.c:1525:50: warning: invalid assignment: ^=
> drivers/net/ethernet/qlogic/qede/qede_fp.c:1525:50:    left side has type restricted __le16
> drivers/net/ethernet/qlogic/qede/qede_fp.c:1525:50:    right side has type int
> drivers/net/ethernet/qlogic/qede/qede_fp.c:1590:42: warning: invalid assignment: |=
> drivers/net/ethernet/qlogic/qede/qede_fp.c:1590:42:    left side has type restricted __le16
> drivers/net/ethernet/qlogic/qede/qede_fp.c:1590:42:    right side has type unsigned int
> drivers/net/ethernet/qlogic/qede/qede_ethtool.c:1315:34: warning: invalid assignment: |=
> drivers/net/ethernet/qlogic/qede/qede_ethtool.c:1315:34:    left side has type restricted __le16
> drivers/net/ethernet/qlogic/qede/qede_ethtool.c:1315:34:    right side has type int
> drivers/net/ethernet/qlogic/qede/qede_ethtool.c:1330:13: warning: incorrect type in assignment (different base types)
> drivers/net/ethernet/qlogic/qede/qede_ethtool.c:1330:13:    expected int [signed] [assigned] val
> drivers/net/ethernet/qlogic/qede/qede_ethtool.c:1330:13:    got restricted __le16 [usertype] <noident>
> drivers/net/ethernet/qlogic/qede/qede_ethtool.c:1331:33: warning: incorrect type in assignment (different base types)
> drivers/net/ethernet/qlogic/qede/qede_ethtool.c:1331:33:    expected restricted __le16 [usertype] bd_prod
> drivers/net/ethernet/qlogic/qede/qede_ethtool.c:1331:33:    got int [signed] [assigned] val
> drivers/net/ethernet/qlogic/qede/qede_roce.c:224:29: warning: symbol 'qede_roce_get_free_event_node' was not declared. Should it be static?
> 
> Do you want us to re-spin the series with the updated commit message?

Where in that log above does it say that the method is defined twice
in qede_dcbnl_ops?

I hate to say this, but this is why I get frustrated with such across
the board cleanups with empty commit messages.

  reply	other threads:[~2017-05-22 18:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-22 11:32 [PATCH net-next 00/11] qed/qede: Mostly-cleanup series Yuval Mintz
2017-05-22 11:32 ` [PATCH net-next 01/11] qede: Fix sparse warnings Yuval Mintz
2017-05-22 16:38   ` David Miller
2017-05-22 16:48     ` Mintz, Yuval
2017-05-22 16:54       ` David Miller
2017-05-22 17:44         ` Mintz, Yuval
2017-05-22 18:29           ` David Miller [this message]
2017-05-22 11:32 ` [PATCH net-next 02/11] qed: Align DP_ERR style with other DP macros Yuval Mintz
2017-05-22 11:32 ` [PATCH net-next 03/11] qed: !main_ptt for tunnel configuration Yuval Mintz
2017-05-22 11:32 ` [PATCH net-next 04/11] qed: Log incorrectly installed board Yuval Mintz
2017-05-22 11:32 ` [PATCH net-next 05/11] qed: Drop the 's' from num_ports_in_engines Yuval Mintz
2017-05-22 11:32 ` [PATCH net-next 06/11] qed: Remove BB_A0 references Yuval Mintz
2017-05-22 11:32 ` [PATCH net-next 07/11] qed: Flush slowpath tasklet on stop Yuval Mintz
2017-05-22 11:32 ` [PATCH net-next 08/11] qed: Enable RoCE parser searching on fp init Yuval Mintz
2017-05-22 11:32 ` [PATCH net-next 09/11] qed: Provide MBI information in dev_info Yuval Mintz
2017-05-22 11:32 ` [PATCH net-next 10/11] qede: Log probe of PCI device Yuval Mintz
2017-05-22 11:32 ` [PATCH net-next 11/11] qed: Replace set_id() api with set_name() Yuval Mintz

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=20170522.142903.2151382146475588141.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=Manish.Chopra@cavium.com \
    --cc=Yuval.Mintz@cavium.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).