From: Randy Dunlap <randy.dunlap@oracle.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Subject: Re: linux-next: Tree for November 19 (rtmutex)
Date: Thu, 2 Dec 2010 11:52:48 -0800 [thread overview]
Message-ID: <20101202115248.f88d7f56.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20101119091629.ddf35bec.randy.dunlap@oracle.com>
On Fri, 19 Nov 2010 09:16:29 -0800 Randy Dunlap wrote:
> On Fri, 19 Nov 2010 14:32:07 +1100 Stephen Rothwell wrote:
>
> > Hi all,
> >
> > Changes since 20101118:
>
>
> when CONFIG_RT_MUTEXES is not enabled:
>
> kernel/rtmutex_common.h:81: error: 'struct task_struct' has no member named 'pi_waiters'
> kernel/rtmutex_common.h:87: error: 'struct task_struct' has no member named 'pi_waiters'
This build error still occurs in linux-next 20101202.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-12-02 19:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 3:32 linux-next: Tree for November 19 Stephen Rothwell
2010-11-19 17:15 ` linux-next: Tree for November 19 (sched_fair) Randy Dunlap
2010-11-19 17:16 ` linux-next: Tree for November 19 (rtmutex) Randy Dunlap
2010-12-02 19:52 ` Randy Dunlap [this message]
2010-11-19 17:30 ` [PATCH -next] staging: fix winbond build, needs delay.h Randy Dunlap
2010-11-19 17:37 ` Pavel Machek
2010-11-19 17:38 ` Greg KH
2010-11-19 17:48 ` Randy Dunlap
2010-11-19 17:54 ` Greg KH
2010-11-19 17:40 ` linux-next: Tree for November 19 Zimny Lech
2010-11-19 17:42 ` Alan Cox
2010-11-19 18:35 ` Zimny Lech
2010-11-20 5:50 ` Zimny Lech
2010-11-20 5:52 ` Zimny Lech
2010-11-20 10:44 ` Jens Axboe
2010-11-20 7:15 ` Zimny Lech
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=20101202115248.f88d7f56.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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.