[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <C27F8246C663564A84BB7AB343977242178EE78068@IRVEXCHCCR01.corp.ad.broadcom.com>
Date: Sun, 14 Jun 2009 07:51:07 -0700
From: "Michael Chan" <mchan@...adcom.com>
To: "'James Bottomley'" <James.Bottomley@...senPartnership.com>
cc: "Linus Torvalds" <torvalds@...ux-foundation.org>,
"Ingo Molnar" <mingo@...e.hu>,
"Randy Dunlap" <randy.dunlap@...cle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"David S. Miller" <davem@...emloft.net>,
linux-scsi <linux-scsi@...r.kernel.org>
Subject: Re: -git tree build failure #2: drivers/net/cnic.c:2520: error:
implicit declaration of function '__symbol_get'
James Bottomley wrote:
> On Sat, 2009-06-13 at 19:18 -0700, Michael Chan wrote:
> >
> > This will require some additional infra-structure. We can look into
> > this when we support the 10G driver. Thanks.
>
> So if you're going to redo it for the 10G driver, and without the 10G
> driver there really seems no need to have a call by
> reflection in there,
> why not simply do a direct call until the 10G driver is added? This
> will save everyone potential hassle from what is a highly unusual
> interface.
>
There's an additional usage issue if we switch to a direct call. The
cnic driver will now have a permanent reference on the bnx2 driver
after it is loaded. Networking users will be unable to unload the
bnx2 driver once the cnic driver is loaded.
This may not be a serious issue, but one of the goals of the design is
to have minmal impact on networking users. Since kernel 2.6, users
have been able to unload networking drivers at any time.
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists