From: Greg KH <gregkh@suse.de>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-ia64@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Steven Rostedt <rostedt@goodmis.org>,
linux-wireless@vger.kernel.org, Mark Fasheh <mfasheh@suse.com>,
Joel Becker <Joel.Becker@oracle.com>
Subject: Re: linux-next: Tree for October 28
Date: Wed, 29 Oct 2008 16:01:26 +0000 [thread overview]
Message-ID: <20081029160126.GA19132@suse.de> (raw)
In-Reply-To: <20081029125449.GD24103@tuxdriver.com>
On Wed, Oct 29, 2008 at 08:54:49AM -0400, John W. Linville wrote:
> On Tue, Oct 28, 2008 at 10:07:41PM -0700, Andrew Morton wrote:
> > On Tue, 28 Oct 2008 18:30:55 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > > I have created today's linux-next tree at
> > > git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
> > > (patches at
> > > http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/).
>
> > and wireless needs some Kconfig help. Please don't just break other
> > architecture's build like this.
> >
> > drivers/staging/wlan-ng/wlan_compat.h:136:3: #error "No CPU identified!"
> > drivers/staging/wlan-ng/wlan_compat.h:695:6: warning: "WLAN_CPU_FAMILY" is not defined
> > drivers/staging/wlan-ng/wlan_compat.h:699:6: warning: "WLAN_CPU_FAMILY" is not defined
>
> For the record, I blame Greg K-H for this... :-)
Ick, yes, _ANYTHING_ in drivers/staging/ is my fault, please let me know
about this.
I'll fix this up, thanks for the report.
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@suse.de>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-ia64@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Steven Rostedt <rostedt@goodmis.org>,
linux-wireless@vger.kernel.org, Mark Fasheh <mfasheh@suse.com>,
Joel Becker <Joel.Becker@oracle.com>
Subject: Re: linux-next: Tree for October 28
Date: Wed, 29 Oct 2008 09:01:26 -0700 [thread overview]
Message-ID: <20081029160126.GA19132@suse.de> (raw)
In-Reply-To: <20081029125449.GD24103@tuxdriver.com>
On Wed, Oct 29, 2008 at 08:54:49AM -0400, John W. Linville wrote:
> On Tue, Oct 28, 2008 at 10:07:41PM -0700, Andrew Morton wrote:
> > On Tue, 28 Oct 2008 18:30:55 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > > I have created today's linux-next tree at
> > > git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
> > > (patches at
> > > http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/).
>
> > and wireless needs some Kconfig help. Please don't just break other
> > architecture's build like this.
> >
> > drivers/staging/wlan-ng/wlan_compat.h:136:3: #error "No CPU identified!"
> > drivers/staging/wlan-ng/wlan_compat.h:695:6: warning: "WLAN_CPU_FAMILY" is not defined
> > drivers/staging/wlan-ng/wlan_compat.h:699:6: warning: "WLAN_CPU_FAMILY" is not defined
>
> For the record, I blame Greg K-H for this... :-)
Ick, yes, _ANYTHING_ in drivers/staging/ is my fault, please let me know
about this.
I'll fix this up, thanks for the report.
greg k-h
next prev parent reply other threads:[~2008-10-29 16:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 7:30 linux-next: Tree for October 28 Stephen Rothwell
2008-10-28 23:00 ` Andrew Morton
2008-10-28 23:23 ` Andrew Morton
2008-10-29 8:21 ` Ingo Molnar
2008-10-29 7:49 ` Ingo Molnar
2008-10-29 5:07 ` Andrew Morton
2008-10-29 5:07 ` Andrew Morton
2008-10-29 12:01 ` Johannes Berg
2008-10-29 12:01 ` Johannes Berg
2008-10-29 12:54 ` John W. Linville
2008-10-29 12:54 ` John W. Linville
2008-10-29 16:01 ` Greg KH [this message]
2008-10-29 16:01 ` Greg KH
2008-10-29 21:39 ` Mark Fasheh
2008-10-29 21:39 ` Mark Fasheh
2008-10-29 21:39 ` Mark Fasheh
-- strict thread matches above, loose matches on Subject: below --
2009-10-28 8:06 Stephen Rothwell
2010-10-28 3:20 Stephen Rothwell
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=20081029160126.GA19132@suse.de \
--to=gregkh@suse.de \
--cc=Joel.Becker@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mfasheh@suse.com \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
/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.