All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
To: Randy Dunlap <rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
Cc: Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>,
	linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: linux-next: Tree for Dec 14 (phy vs. bcma)
Date: Wed, 14 Dec 2011 15:08:41 -0500	[thread overview]
Message-ID: <20111214200841.GC2607@tuxdriver.com> (raw)
In-Reply-To: <4EE90EB1.4060903-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>

On Wed, Dec 14, 2011 at 01:01:37PM -0800, Randy Dunlap wrote:
> On 12/13/2011 11:26 PM, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Changes since 20111213:
> 
> 
> drivers/built-in.o: In function `b43_nphy_pmu_spur_avoid.clone.8':
> phy_n.c:(.text+0x1589d8): undefined reference to `bcma_chipco_pll_write'
> phy_n.c:(.text+0x1589e9): undefined reference to `bcma_chipco_pll_write'
> phy_n.c:(.text+0x1589fa): undefined reference to `bcma_chipco_pll_write'
> phy_n.c:(.text+0x158a08): undefined reference to `bcma_chipco_pll_write'
> phy_n.c:(.text+0x158a1d): undefined reference to `bcma_chipco_pll_write'
> drivers/built-in.o:phy_n.c:(.text+0x158a2e): more undefined references to `bcma_chipco_pll_write' follow
> 
> 
> BCMA is not enabled.
> Full randconfig file is attached.

I've already merged a patch to address this.

Thanks,

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org			might be all we have.  Be ready.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: "John W. Linville" <linville@tuxdriver.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: linux-next: Tree for Dec 14 (phy vs. bcma)
Date: Wed, 14 Dec 2011 15:08:41 -0500	[thread overview]
Message-ID: <20111214200841.GC2607@tuxdriver.com> (raw)
In-Reply-To: <4EE90EB1.4060903@xenotime.net>

On Wed, Dec 14, 2011 at 01:01:37PM -0800, Randy Dunlap wrote:
> On 12/13/2011 11:26 PM, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Changes since 20111213:
> 
> 
> drivers/built-in.o: In function `b43_nphy_pmu_spur_avoid.clone.8':
> phy_n.c:(.text+0x1589d8): undefined reference to `bcma_chipco_pll_write'
> phy_n.c:(.text+0x1589e9): undefined reference to `bcma_chipco_pll_write'
> phy_n.c:(.text+0x1589fa): undefined reference to `bcma_chipco_pll_write'
> phy_n.c:(.text+0x158a08): undefined reference to `bcma_chipco_pll_write'
> phy_n.c:(.text+0x158a1d): undefined reference to `bcma_chipco_pll_write'
> drivers/built-in.o:phy_n.c:(.text+0x158a2e): more undefined references to `bcma_chipco_pll_write' follow
> 
> 
> BCMA is not enabled.
> Full randconfig file is attached.

I've already merged a patch to address this.

Thanks,

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  parent reply	other threads:[~2011-12-14 20:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-14  7:26 linux-next: Tree for Dec 14 Stephen Rothwell
2011-12-14 21:01 ` linux-next: Tree for Dec 14 (phy vs. bcma) Randy Dunlap
     [not found]   ` <4EE90EB1.4060903-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
2011-12-14 20:08     ` John W. Linville [this message]
2011-12-14 20:08       ` John W. Linville
2011-12-14 21:05 ` linux-next: Tree for Dec 14 (net) Randy Dunlap
2011-12-14 21:21 ` linux-next: Tree for Dec 14 (mlx4) Randy Dunlap

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=20111214200841.GC2607@tuxdriver.com \
    --to=linville-2xusbdqka4r54taoqtywwq@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org \
    --cc=sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.