netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: David Miller <davem@davemloft.net>,
	lkp@intel.com, kbuild-all@01.org, netdev@vger.kernel.org,
	oss-drivers@netronome.com, andrew@lunn.ch, f.fainelli@gmail.com,
	mkubecek@suse.cz, eugenem@fb.com, jonathan.lemon@gmail.com
Subject: Re: [PATCH net-next v3 8/8] ethtool: add compat for devlink info
Date: Fri, 1 Feb 2019 08:57:14 +0100	[thread overview]
Message-ID: <20190201075714.GA2401@nanopsycho> (raw)
In-Reply-To: <20190131092925.2106513e@cakuba.hsd1.ca.comcast.net>

Thu, Jan 31, 2019 at 06:29:25PM CET, jakub.kicinski@netronome.com wrote:
>On Thu, 31 Jan 2019 09:25:08 -0800, Jakub Kicinski wrote:
>> On Thu, 31 Jan 2019 09:23:03 -0800 (PST), David Miller wrote:
>> > From: kbuild test robot <lkp@intel.com>
>> > Date: Fri, 1 Feb 2019 00:19:33 +0800
>> >   
>> > > All errors (new ones prefixed by >>):
>> > > 
>> > >    m68k-linux-gnu-ld: drivers/rtc/proc.o: in function `is_rtc_hctosys.isra.0':
>> > >    proc.c:(.text+0x178): undefined reference to `strcmp'
>> > >    m68k-linux-gnu-ld: net/core/ethtool.o: in function `ethtool_get_drvinfo':    
>> > >>> ethtool.c:(.text+0xc08): undefined reference to `devlink_compat_running_version'    
>> > 
>> > Missing string.h include perhaps?  
>> 
>> Yeah, that one looks like existing m68k bug, but also I think I need to
>> cater to the DEVLINK=m case since ethtool code is always built in we
>> can't use the MAY_USE_DEVLINK trick :S
>
>I think we have to do this:
>
>#if IS_REACHABLE(CONFIG_NET_DEVLINK)
>void devlink_compat_running_version(struct net_device *dev,
>				    char *buf, size_t len);
>#else
>static inline void
>devlink_compat_running_version(struct net_device *dev, char *buf, size_t len)
>{
>}
>#endif
>
>Jiri, any objections?

Np.

      reply	other threads:[~2019-02-01  8:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-30 23:41 [PATCH net-next v3 0/8] devlink: add device (driver) information API Jakub Kicinski
2019-01-30 23:41 ` [PATCH net-next v3 1/8] devlink: add device " Jakub Kicinski
2019-01-31  7:40   ` Jiri Pirko
2019-01-30 23:41 ` [PATCH net-next v3 2/8] devlink: add version reporting to devlink info API Jakub Kicinski
2019-01-31  7:57   ` Jiri Pirko
2019-01-30 23:41 ` [PATCH net-next v3 3/8] devlink: add generic info version names Jakub Kicinski
2019-01-31  7:58   ` Jiri Pirko
2019-01-30 23:41 ` [PATCH net-next v3 4/8] nfp: devlink: report driver name and serial number Jakub Kicinski
2019-01-31  7:59   ` Jiri Pirko
2019-01-30 23:41 ` [PATCH net-next v3 5/8] nfp: devlink: report fixed versions Jakub Kicinski
2019-01-31  8:00   ` Jiri Pirko
2019-01-30 23:41 ` [PATCH net-next v3 6/8] nfp: nsp: add support for versions command Jakub Kicinski
2019-01-30 23:41 ` [PATCH net-next v3 7/8] nfp: devlink: report the running and flashed versions Jakub Kicinski
2019-01-31  8:03   ` Jiri Pirko
2019-01-30 23:41 ` [PATCH net-next v3 8/8] ethtool: add compat for devlink info Jakub Kicinski
2019-01-31 16:19   ` kbuild test robot
2019-01-31 17:23     ` David Miller
2019-01-31 17:25       ` Jakub Kicinski
2019-01-31 17:29         ` Jakub Kicinski
2019-02-01  7:57           ` Jiri Pirko [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=20190201075714.GA2401@nanopsycho \
    --to=jiri@resnulli.us \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=eugenem@fb.com \
    --cc=f.fainelli@gmail.com \
    --cc=jakub.kicinski@netronome.com \
    --cc=jonathan.lemon@gmail.com \
    --cc=kbuild-all@01.org \
    --cc=lkp@intel.com \
    --cc=mkubecek@suse.cz \
    --cc=netdev@vger.kernel.org \
    --cc=oss-drivers@netronome.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;
as well as URLs for NNTP newsgroup(s).