Netdev List
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Kyle Roeschley <kyle.roeschley@ni.com>
Cc: kbuild-all@01.org, Andrew Lunn <andrew@lunn.ch>,
	Florian Fainelli <f.fainelli@gmail.com>,
	"David S . Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Kyle Roeschley <kyle.roeschley@ni.com>
Subject: Re: [PATCH v2] net: phy: leds: Don't make our own link speed names
Date: Sat, 10 Nov 2018 07:08:56 +0800	[thread overview]
Message-ID: <201811100748.1CYxXmRQ%fengguang.wu@intel.com> (raw)
In-Reply-To: <20181108210310.32606-1-kyle.roeschley@ni.com>

[-- Attachment #1: Type: text/plain, Size: 2041 bytes --]

Hi Kyle,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on net-next/master]
[also build test WARNING on v4.20-rc1 next-20181109]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Kyle-Roeschley/net-phy-leds-Don-t-make-our-own-link-speed-names/20181109-143344
config: x86_64-allmodconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All warnings (new ones prefixed by >>):

>> drivers/net/phy/phy_led_triggers.c:82:53: warning: incorrect type in argument 4 (different modifiers)
   drivers/net/phy/phy_led_triggers.c:82:53:    expected char *suffix
   drivers/net/phy/phy_led_triggers.c:82:53:    got char const *
   drivers/net/phy/phy_led_triggers.c: In function 'phy_led_trigger_register':
   drivers/net/phy/phy_led_triggers.c:82:9: warning: passing argument 4 of 'phy_led_trigger_format_name' discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers]
            phy_speed_to_str(speed));
            ^~~~~~~~~~~~~~~~
   drivers/net/phy/phy_led_triggers.c:69:13: note: expected 'char *' but argument is of type 'const char *'
    static void phy_led_trigger_format_name(struct phy_device *phy, char *buf,
                ^~~~~~~~~~~~~~~~~~~~~~~~~~~

vim +82 drivers/net/phy/phy_led_triggers.c

    75	
    76	static int phy_led_trigger_register(struct phy_device *phy,
    77					    struct phy_led_trigger *plt,
    78					    unsigned int speed)
    79	{
    80		plt->speed = speed;
    81		phy_led_trigger_format_name(phy, plt->name, sizeof(plt->name),
  > 82					    phy_speed_to_str(speed));
    83		plt->trigger.name = plt->name;
    84	
    85		return led_trigger_register(&plt->trigger);
    86	}
    87	

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 66569 bytes --]

      parent reply	other threads:[~2018-11-09 23:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08 21:03 [PATCH v2] net: phy: leds: Don't make our own link speed names Kyle Roeschley
2018-11-09  7:44 ` kbuild test robot
2018-11-09 23:08 ` kbuild test robot [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=201811100748.1CYxXmRQ%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=kbuild-all@01.org \
    --cc=kyle.roeschley@ni.com \
    --cc=linux-kernel@vger.kernel.org \
    --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