From: kbuild test robot <lkp@intel.com> To: Yangbo Lu <yangbo.lu@nxp.com> Cc: kbuild-all@lists.01.org, Vladimir Oltean <vladimir.oltean@nxp.com>, Claudiu Manoil <claudiu.manoil@nxp.com>, Andrew Lunn <andrew@lunn.ch>, Vivien Didelot <vivien.didelot@gmail.com>, Florian Fainelli <f.fainelli@gmail.com>, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [RFC PATCH linux-next] net: dsa: ocelot: felix_txtstamp() can be static Date: Sat, 23 Nov 2019 06:50:29 +0800 [thread overview] Message-ID: <20191122225029.ckppkwdle3yzaoq7@4978f4969bb8> (raw) In-Reply-To: <201911230623.rJBgtgcn%lkp@intel.com> Fixes: c0bcf537667c ("net: dsa: ocelot: add hardware timestamping support for Felix") Signed-off-by: kbuild test robot <lkp@intel.com> --- felix.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/net/dsa/ocelot/felix.c b/drivers/net/dsa/ocelot/felix.c index 167e41549cdd1..b7f92464815d7 100644 --- a/drivers/net/dsa/ocelot/felix.c +++ b/drivers/net/dsa/ocelot/felix.c @@ -348,8 +348,8 @@ static bool felix_rxtstamp(struct dsa_switch *ds, int port, return false; } -bool felix_txtstamp(struct dsa_switch *ds, int port, - struct sk_buff *clone, unsigned int type) +static bool felix_txtstamp(struct dsa_switch *ds, int port, + struct sk_buff *clone, unsigned int type) { struct ocelot *ocelot = ds->priv; struct ocelot_port *ocelot_port = ocelot->ports[port];
WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com> To: kbuild-all@lists.01.org Subject: [RFC PATCH linux-next] net: dsa: ocelot: felix_txtstamp() can be static Date: Sat, 23 Nov 2019 06:50:29 +0800 [thread overview] Message-ID: <20191122225029.ckppkwdle3yzaoq7@4978f4969bb8> (raw) In-Reply-To: <201911230623.rJBgtgcn%lkp@intel.com> [-- Attachment #1: Type: text/plain, Size: 834 bytes --] Fixes: c0bcf537667c ("net: dsa: ocelot: add hardware timestamping support for Felix") Signed-off-by: kbuild test robot <lkp@intel.com> --- felix.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/net/dsa/ocelot/felix.c b/drivers/net/dsa/ocelot/felix.c index 167e41549cdd1..b7f92464815d7 100644 --- a/drivers/net/dsa/ocelot/felix.c +++ b/drivers/net/dsa/ocelot/felix.c @@ -348,8 +348,8 @@ static bool felix_rxtstamp(struct dsa_switch *ds, int port, return false; } -bool felix_txtstamp(struct dsa_switch *ds, int port, - struct sk_buff *clone, unsigned int type) +static bool felix_txtstamp(struct dsa_switch *ds, int port, + struct sk_buff *clone, unsigned int type) { struct ocelot *ocelot = ds->priv; struct ocelot_port *ocelot_port = ocelot->ports[port];
next prev parent reply other threads:[~2019-11-22 22:51 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-11-22 22:50 [linux-next:master 13276/13503] drivers/net/dsa/ocelot/felix.c:351:6: sparse: sparse: symbol 'felix_txtstamp' was not declared. Should it be static? kbuild test robot 2019-11-22 22:50 ` kbuild test robot 2019-11-22 22:50 ` kbuild test robot [this message] 2019-11-22 22:50 ` [RFC PATCH linux-next] net: dsa: ocelot: felix_txtstamp() can be static kbuild test robot
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=20191122225029.ckppkwdle3yzaoq7@4978f4969bb8 \ --to=lkp@intel.com \ --cc=andrew@lunn.ch \ --cc=claudiu.manoil@nxp.com \ --cc=f.fainelli@gmail.com \ --cc=kbuild-all@lists.01.org \ --cc=linux-kernel@vger.kernel.org \ --cc=netdev@vger.kernel.org \ --cc=vivien.didelot@gmail.com \ --cc=vladimir.oltean@nxp.com \ --cc=yangbo.lu@nxp.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.