From: Ingo Molnar <mingo@elte.hu>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: David Miller <davem@davemloft.net>,
randy.dunlap@oracle.com, linux-kernel@vger.kernel.org,
mchan@broadcom.com, torvalds@linux-foundation.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: -git tree build failure in drivers/net/cnic.c: undefined reference to `ip6_route_output'
Date: Sat, 13 Jun 2009 08:42:53 +0200 [thread overview]
Message-ID: <20090613064253.GB14034@elte.hu> (raw)
In-Reply-To: <1244851393.26552.1.camel@mulgrave.site>
* James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
> On Fri, 2009-06-12 at 16:51 -0700, David Miller wrote:
> > From: Randy Dunlap <randy.dunlap@oracle.com>
> > Date: Fri, 12 Jun 2009 11:43:48 -0700
> >
> > > Ingo Molnar wrote:
> > >> today's -git fails to build with ipv6 disabled (x86):
> > >>
> > >> drivers/built-in.o: In function `cnic_get_v6_route':
> > >> cnic.c:(.text+0x104c42): undefined reference to `ip6_route_output'
> > >>
> > >> introduced by this new driver:
> > >>
> > >> a463696: [SCSI] cnic: Add new Broadcom CNIC driver.
> > >
> > > I just posted a patch for this to netdev and it was acked by its maintainer.
> > > Patch is below.
> >
> > I was hoping the scsi folks, or Linus directly, would pick this up.
>
> I can, but my first tree's just gone ... the next one won't be
> going until nearer the merge window.
The thing is, this driver has been submitted 4 days ago, merged by
you 3 days ago and sent upstream two days ago. It has two build
breakages so far, the first one of which triggered on a pretty
common config too.
If you have time for such speedy integration but then dont have time
to test on common configs and dont have time to follow up on and
fix/merge the (pretty much inevitable) upstream breakages you
introduce and get the fixes to Linus, sending prompt fixes next-day
preferably, out of your usual schedule, it would be a better
solution for you to submit new drivers to the staging tree i think -
which does have the capacity to fix and merge such stuff.
Ingo
next prev parent reply other threads:[~2009-06-13 6:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 18:43 Ingo Molnar
2009-06-12 18:43 ` Randy Dunlap
2009-06-12 23:51 ` David Miller
2009-06-13 0:03 ` James Bottomley
2009-06-13 0:05 ` David Miller
2009-06-13 14:37 ` James Bottomley
2009-06-13 6:42 ` Ingo Molnar [this message]
2009-06-13 7:03 ` Michael Chan
2009-06-13 6:29 ` -git tree build failure #2: drivers/net/cnic.c:2520: error: implicit declaration of function ‘__symbol_get’ Ingo Molnar
2009-06-13 20:11 ` Linus Torvalds
2009-06-13 20:31 ` Ingo Molnar
2009-06-13 20:35 ` Ingo Molnar
2009-06-13 20:46 ` Ingo Molnar
2009-06-13 20:42 ` James Bottomley
2009-06-14 0:43 ` Michael Chan
2009-06-14 1:33 ` James Bottomley
2009-06-14 2:18 ` Michael Chan
2009-06-14 14:15 ` James Bottomley
2009-06-14 14:51 ` -git tree build failure #2: drivers/net/cnic.c:2520: error: implicit declaration of function '__symbol_get' Michael Chan
2009-06-15 1:27 ` -git tree build failure #2: drivers/net/cnic.c:2520: error: implicit declaration of function ‘__symbol_get’ Mike Christie
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=20090613064253.GB14034@elte.hu \
--to=mingo@elte.hu \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mchan@broadcom.com \
--cc=randy.dunlap@oracle.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®