From: Anish Bhatt <anish@chelsio.com>
To: netdev@vger.kernel.org
Cc: linux-scsi@vger.kernel.org, davem@davemloft.net,
JBottomley@parallels.com, mchan@broadcom.com,
eddie.wai@broadcom.com, rdunlap@infradead.org,
jim.epost@gmail.com, Anish Bhatt <anish@chelsio.com>
Subject: [PATCH net 0/2] Fix randconfig errros in bnx2i/bnx2fc caused by IPV6
Date: Mon, 15 Sep 2014 13:45:19 -0700 [thread overview]
Message-ID: <1410813921-24400-1-git-send-email-anish@chelsio.com> (raw)
Just like CNIC bnx2i/bnx2fc also have their tristate dependent on IPV6, however
using the same solution as CNIC can cause recursive dependecies during make.
Based on suggestions by Randy Dunlap, SCSI_NETLINK now depends on NET instead
of selecting NET. Second patch fixes the actual randconfig error.
Entire thread can be followed here : https://lkml.org/lkml/2014/9/9/500
-Anish
Fixes: c99d667e8527 ("cnic : Cleanup CONFIG_IPV6 & VLAN check")
Anish Bhatt (2):
scsi_netlink : Make SCSI_NETLINK dependent on NET instead of selecting
NET
bnx2i/bnx2fc : fix randconfig error
drivers/scsi/Kconfig | 2 +-
drivers/scsi/bnx2fc/Kconfig | 1 +
drivers/scsi/bnx2i/Kconfig | 1 +
3 files changed, 3 insertions(+), 1 deletion(-)
--
2.1.0
next reply other threads:[~2014-09-15 20:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 20:45 Anish Bhatt [this message]
2014-09-15 20:45 ` [PATCH net 1/2] scsi_netlink : Make SCSI_NETLINK dependent on NET instead of selecting NET Anish Bhatt
2014-09-16 0:20 ` [PATCH 3] scsi: fix build errors, SCSI_FC_ATTRS needs to depend on SCSI && NET Randy Dunlap
2014-09-16 3:00 ` Anish Bhatt
2014-09-16 3:17 ` Randy Dunlap
2014-09-16 4:11 ` Anish Bhatt
2014-09-16 4:07 ` David Miller
2014-09-15 20:45 ` [PATCH net 2/2] bnx2i/bnx2fc : fix randconfig error in next-20140909 Anish Bhatt
2014-09-15 21:45 ` [PATCH net 0/2] Fix randconfig errros in bnx2i/bnx2fc caused by IPV6 David Miller
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=1410813921-24400-1-git-send-email-anish@chelsio.com \
--to=anish@chelsio.com \
--cc=JBottomley@parallels.com \
--cc=davem@davemloft.net \
--cc=eddie.wai@broadcom.com \
--cc=jim.epost@gmail.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mchan@broadcom.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;
as well as URLs for NNTP newsgroup(s).