From: David Miller <davem@davemloft.net>
To: fengguang.wu@intel.com
Cc: manish.chopra@cavium.com, kbuild-all@01.org,
netdev@vger.kernel.org, ariel.elior@cavium.com,
everest-linux-l2@cavium.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH net-next] qed/qede: qede_setup_tc() can be static
Date: Fri, 10 Aug 2018 14:42:24 -0700 (PDT) [thread overview]
Message-ID: <20180810.144224.1142211723851962889.davem@davemloft.net> (raw)
In-Reply-To: <20180810012959.GA22458@athens>
From: kbuild test robot <fengguang.wu@intel.com>
Date: Fri, 10 Aug 2018 09:29:59 +0800
> Fixes: 5e7baf0fcb2a ("qed/qede: Multi CoS support.")
> Signed-off-by: kbuild test robot <fengguang.wu@intel.com>
Applied.
prev parent reply other threads:[~2018-08-10 21:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 1:29 [net-next:master 1939/1953] drivers/net/ethernet/qlogic/qede/qede_main.c:539:5: sparse: symbol 'qede_setup_tc' was not declared. Should it be static? kbuild test robot
2018-08-10 1:29 ` [RFC PATCH net-next] qed/qede: qede_setup_tc() can be static kbuild test robot
2018-08-10 21:42 ` 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=20180810.144224.1142211723851962889.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ariel.elior@cavium.com \
--cc=everest-linux-l2@cavium.com \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manish.chopra@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).