From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux NICS <linux.nics@intel.com>
Subject: Re: [PATCH -next] net: i40e: fix build, depends on CONFIGFS_FS
Date: Tue, 03 Mar 2015 12:11:10 -0800 [thread overview]
Message-ID: <1425413470.2556.78.camel@jtkirshe-mobl> (raw)
In-Reply-To: <54F60D0A.6020903@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]
On Tue, 2015-03-03 at 11:35 -0800, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
>
> i40e uses configfs interfaces so it should depend on CONFIGFS_FS.
>
> Fixes these build errors:
>
> drivers/built-in.o: In function `i40e_cfgfs_group_make_item':
> i40e_configfs.c:(.text+0x2fcdca): undefined reference to
> `config_item_init_type_name'
> drivers/built-in.o: In function `i40e_configfs_init':
> (.text+0x2fcee6): undefined reference to `config_group_init'
> drivers/built-in.o: In function `i40e_configfs_init':
> (.text+0x2fcf0c): undefined reference to `configfs_register_subsystem'
> drivers/built-in.o: In function `i40e_configfs_exit':
> (.text+0x2fcf71): undefined reference to
> `configfs_unregister_subsystem'
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Linux NICS <linux.nics@intel.com>
> Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> ---
> drivers/net/ethernet/intel/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
I have a patch from Greg Rose already that fixes this, which I was just
about to push.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-03-03 20:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 19:35 [PATCH -next] net: i40e: fix build, depends on CONFIGFS_FS Randy Dunlap
2015-03-03 20:02 ` David Miller
2015-03-03 20:23 ` Jeff Kirsher
2015-03-03 20:11 ` Jeff Kirsher [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=1425413470.2556.78.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.nics@intel.com \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.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