From: Philipp Reisner <philipp.reisner@linbit.com>
To: Lars Ellenberg <lars.ellenberg@linbit.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: linux-next: drbd tree build failure
Date: Mon, 27 Jul 2009 19:17:55 +0200 [thread overview]
Message-ID: <200907271917.56148.philipp.reisner@linbit.com> (raw)
In-Reply-To: <20090727080957.GA8046@barkeeper1-xen.linbit>
On Monday 27 July 2009 10:09:57 Lars Ellenberg wrote:
> On Mon, Jul 27, 2009 at 03:48:16PM +1000, Stephen Rothwell wrote:
> > Hi Philipp,
> >
> > Today's linux-next build (x86_64 allmodconfig) failed like this:
> >
> > drivers/block/drbd/drbd_main.c: In function
> > 'drbd_thread_current_set_cpu': drivers/block/drbd/drbd_main.c:1592:
> > error: implicit declaration of function 'set_cpus_allowed'
> >
> > Introduced by commit 8a4ebc3fbd90072ac870064a930fe612eea6d9a1 ("DRBD:
> > main") from the drbd interacting with commit
> > 84cf7f02712e3491fb9776f950a8c4f413204c8b
> > ("cpumask:remove-set_cpus_allowed") from the rr tree.
> >
> > I am not sure what the transformation to the new infrastructure is here -
> > maybe Rusty can help?
> >
> > For today, I have reverted the rr tree commit above but we need a better
> > solution.
>
> I think we can easily use set_cpus_allowed_ptr() instead,
> as in fact, we do not have the cpu mask on the stack.
> But embeded in struct drbd_conf.
Ok. Lars' patch is now complete and arrived in the git tree...
It should build now with Rusty's paches.
-phil
--
: Dipl-Ing Philipp Reisner
: LINBIT | Your Way to High Availability
: Tel: +43-1-8178292-50, Fax: +43-1-8178292-82
: http://www.linbit.com
DRBD(R) and LINBIT(R) are registered trademarks of LINBIT, Austria.
next prev parent reply other threads:[~2009-07-27 17:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 5:48 linux-next: drbd tree build failure Stephen Rothwell
2009-07-27 8:09 ` Lars Ellenberg
2009-07-27 17:17 ` Philipp Reisner [this message]
2009-07-28 4:20 ` Stephen Rothwell
2009-07-29 1:40 ` Rusty Russell
2009-07-29 15:11 ` Philipp Reisner
2009-07-27 7:37 Stephen Rothwell
2009-07-27 9:09 ` Philipp Reisner
2009-07-27 11:38 ` Alexander Beregalov
2009-07-27 15:07 ` Philipp Reisner
2009-07-28 4:19 ` Stephen Rothwell
2009-07-28 4:20 ` Stephen Rothwell
2009-07-29 5:29 Stephen Rothwell
2009-07-29 6:20 ` Jens Axboe
2009-07-29 15:13 ` Philipp Reisner
2009-07-29 5:29 Stephen Rothwell
2009-07-29 5:47 ` Martin K. Petersen
2009-07-29 6:17 ` Stephen Rothwell
2009-08-18 5:32 ` Stephen Rothwell
2009-08-18 6:01 ` Martin K. Petersen
2009-09-15 6:07 Stephen Rothwell
2009-09-15 6:23 ` Jens Axboe
2009-09-15 6:53 ` Stephen Rothwell
[not found] ` <20090915165309.f07381ec.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2009-09-15 6:57 ` Jens Axboe
2009-09-15 7:45 ` Stephen Rothwell
2009-09-15 14:03 ` Philipp Reisner
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=200907271917.56148.philipp.reisner@linbit.com \
--to=philipp.reisner@linbit.com \
--cc=lars.ellenberg@linbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--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).