From: Greg KH <gregkh@suse.de>
To: Arend Van Spriel <arend@broadcom.com>
Cc: Zimny Lech <napohybelskurwysynom2010@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Brett Rudley <brudley@broadcom.com>,
Henry Ptasinski <henryp@broadcom.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: linux-next: Tree for November 22
Date: Mon, 22 Nov 2010 13:31:22 -0800 [thread overview]
Message-ID: <20101122213122.GA2881@suse.de> (raw)
In-Reply-To: <400C43189542CE41BC0A5B252FC90136952F05944A@SJEXCHCCR02.corp.ad.broadcom.com>
On Mon, Nov 22, 2010 at 12:08:28PM -0800, Arend Van Spriel wrote:
> Hi Greg, Stephen,
>
> The file wl_iw.c declare a struct semaphore variable and uses
> semaphore function, but there is no explicit inclusion of
> <linux/semaphore.h>. I hit this problem last week when trying a
> minimal kernel configuration for my development system. Normally we
> build and test against kernel configuration similar to Ubuntu
> configuration and we got the semaphore definitions for free. Expect a
> patch soon.
Ok, sounds good.
greg k-h
next prev parent reply other threads:[~2010-11-22 21:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 2:49 linux-next: Tree for November 22 Stephen Rothwell
2010-11-22 12:47 ` Zimny Lech
[not found] ` <20101122134911.b7e106f9.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2010-11-22 15:37 ` Zimny Lech
2010-11-22 19:46 ` Greg KH
[not found] ` <20101122194643.GB21985-l3A5Bk7waGM@public.gmane.org>
2010-11-22 20:08 ` Arend Van Spriel
2010-11-22 21:31 ` Greg KH [this message]
2010-11-22 19:55 ` Zimny Lech
2010-11-22 21:26 ` linux-next: Tree for November 22 (kvm) Randy Dunlap
2010-11-29 16:33 ` Randy Dunlap
2010-11-29 16:35 ` Avi Kivity
2010-11-29 17:47 ` Zachary Amsden
2010-11-29 17:52 ` Randy Dunlap
2010-11-29 18:08 ` Zachary Amsden
2010-11-29 19:05 ` Randy Dunlap
2010-11-30 12:17 ` Glauber Costa
2010-11-30 18:09 ` Zachary Amsden
2010-12-10 17:18 ` Randy Dunlap
2010-12-12 9:23 ` Avi Kivity
2010-12-16 9:37 ` Avi Kivity
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=20101122213122.GA2881@suse.de \
--to=gregkh@suse.de \
--cc=arend@broadcom.com \
--cc=brudley@broadcom.com \
--cc=henryp@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=napohybelskurwysynom2010@gmail.com \
--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 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).