public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: 2.6.23-rc8-git4: Known regressions from 2.6.22
Date: Sun, 30 Sep 2007 20:44:36 -0400	[thread overview]
Message-ID: <20071001004436.GA7638@tuxdriver.com> (raw)
In-Reply-To: <alpine.LFD.0.999.0709301443100.3579@woody.linux-foundation.org>

On Sun, Sep 30, 2007 at 02:44:41PM -0700, Linus Torvalds wrote:
> On Sun, 30 Sep 2007, Randy Dunlap wrote:
> > On Sun, 30 Sep 2007 23:05:09 +0200 Rafael J. Wysocki wrote:
> > > 
> > > Subject:	build #301 failed for 2.6.23-rc6-g0d4cbb5 in linux/drivers/net/wireless/libertas/
> > > Submitter:	Toralf Förster <toralf.foerster@gmx.de>
> > > References:	http://lkml.org/lkml/2007/9/11/150
> > > 		http://bugzilla.kernel.org/show_bug.cgi?id=9077
> > > Patch:		http://bugzilla.kernel.org/attachment.cgi?id=12963&action=view
> > 
> > I'm told that this is already patched in the net-2.6.24 git tree,
> > but it should be merged for 2.6.23 IMO.
> 
> Jeff, John?
> 
> Build errors like this may not be a huge deal, but the fix looks 
> worthwhile anyway, so is there any reason this hasn't been sent upstream?

My mistake -- I thought this was a problem introduced in the patches
queued for 2.6.24.

Feel free to pull from here:

	git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git fixes-jgarzik

Thanks!

John

---

The following changes since commit 4942de4a0e914f205d351a81873f4f63986bcc3c:
  Linus Torvalds (1):
        Linux 2.6.23-rc8

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git fixes-jgarzik

Randy Dunlap (1):
      libertas: build problems when partially modular

 drivers/net/wireless/Makefile |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/net/wireless/Makefile b/drivers/net/wireless/Makefile
index ef35bc6..4eb6d97 100644
--- a/drivers/net/wireless/Makefile
+++ b/drivers/net/wireless/Makefile
@@ -43,7 +43,7 @@ obj-$(CONFIG_PCMCIA_RAYCS)	+= ray_cs.o
 obj-$(CONFIG_PCMCIA_WL3501)	+= wl3501_cs.o
 
 obj-$(CONFIG_USB_ZD1201)	+= zd1201.o
-obj-$(CONFIG_LIBERTAS_USB)     += libertas/
+obj-$(CONFIG_LIBERTAS)		+= libertas/
 
 rtl8187-objs		:= rtl8187_dev.o rtl8187_rtl8225.o
 obj-$(CONFIG_RTL8187)	+= rtl8187.o
-- 
John W. Linville
linville@tuxdriver.com

  reply	other threads:[~2007-10-01  1:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-30 21:05 2.6.23-rc8-git4: Known regressions from 2.6.22 Rafael J. Wysocki
2007-09-30 21:30 ` Randy Dunlap
2007-09-30 21:44   ` Linus Torvalds
2007-10-01  0:44     ` John W. Linville [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-09-30 20:49 Rafael J. Wysocki

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=20071001004436.GA7638@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=akpm@linux-foundation.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=rjw@sisk.pl \
    --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