archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <>
To: Stephen Rothwell <>,
	Ralph Campbell <>
Cc:, LKML <>,
Subject: Re: linux-next: Tree for May 27 (infiniband: qib)
Date: Thu, 27 May 2010 09:05:03 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Thu, 27 May 2010 15:26:28 +1000 Stephen Rothwell wrote:

> Hi all,
> We are in the merge window again.  I remind you all not to add stuff for
> 2.6.36 to your linux-next trees until after 2.6.35-rc1.
> Changes since 20100526:


drivers/built-in.o: In function `qib_update_sdma_dca':
qib_iba7322.c:(.text+0x409219): undefined reference to `dca3_get_tag'
drivers/built-in.o: In function `qib_update_rhdrq_dca':
qib_iba7322.c:(.text+0x40a1f9): undefined reference to `dca3_get_tag'
drivers/built-in.o: In function `qib_setup_7322_cleanup':
qib_iba7322.c:(.text+0x40f91f): undefined reference to `dca_remove_requester'
drivers/built-in.o: In function `qib_init_iba7322_funcs':
(.text+0x419b6f): undefined reference to `dca_add_requester'

However, it looks like qib needs to handle DCA config in a way that
is similar to how it is handled in drivers/net/{myri10ge,igb,ixgbe}/
instead of assuming that DCA is enabled.

And please fix the linux-next 2010-may-25 reported qib problem:

*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2010-05-27 16:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-27  5:26 linux-next: Tree for May 27 Stephen Rothwell
2010-05-27 16:05 ` Randy Dunlap [this message]
2010-05-27 21:45   ` linux-next: Tree for May 27 (infiniband: qib) Roland Dreier
2010-05-27 22:06     ` Randy Dunlap
2010-05-27 22:22       ` Ralph Campbell
2010-05-27 16:07 ` [PATCH -next] hid: roccat modules interdependencies Randy Dunlap
2010-05-31 11:58   ` Jiri Kosina

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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).