From: Ingo Molnar <mingo@elte.hu>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-next@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>,
mingo <mingo@redhat.com>, tglx <tglx@linutronix.de>,
hpa <hpa@zytor.com>, akpm <akpm@linux-foundation.org>,
Jens Axboe <jens.axboe@oracle.com>
Subject: Re: [PATCH -next] fork and exit: need to include iocontext.h
Date: Mon, 30 Jun 2008 20:33:37 +0200 [thread overview]
Message-ID: <20080630183337.GD32211@elte.hu> (raw)
In-Reply-To: <20080630112222.f103e477.randy.dunlap@oracle.com>
* Randy Dunlap <randy.dunlap@oracle.com> wrote:
> On Mon, 30 Jun 2008 20:05:06 +0200 Ingo Molnar wrote:
>
> >
> > * Randy Dunlap <randy.dunlap@oracle.com> wrote:
> >
> > > From: Randy Dunlap <randy.dunlap@oracle.com>
> > >
> > > Fix fork and exit build errors: they need to include iocontext.h:
> > >
> > > linux-next-20080630/kernel/fork.c: In function 'copy_process':
> > > linux-next-20080630/kernel/fork.c:1237: error: implicit declaration of function 'put_io_context'
> > > linux-next-20080630/kernel/exit.c: In function 'do_exit':
> > > linux-next-20080630/kernel/exit.c:992: error: implicit declaration of function 'exit_io_context'
> >
> > i havent seen this one - do you know by chance which commit triggers it?
>
>
> Sorry, no idea which commit.
>
> In 50 randconfigs today (next-20080630), I saw this one 12 times.
btw., block.git would be one of my first guesses - Jens Cc:-ed.
normally there's an easy way to find out the source commit of build
failures. Try something like:
git-bisect reset
git-bisect start
git-bisect good v2.6.26-rc8
git-bisect bad linux-next/master
git-bisect run make kernel/fork.o
... this should lead you to the commit that broke the build
automatically. (as long as everyone keeps make oldconfig compatibility)
Ingo
next prev parent reply other threads:[~2008-06-30 18:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-30 17:54 [PATCH -next] fork and exit: need to include iocontext.h Randy Dunlap
2008-06-30 18:05 ` Ingo Molnar
2008-06-30 18:22 ` Randy Dunlap
2008-06-30 18:33 ` Ingo Molnar [this message]
2008-06-30 18:39 ` Randy Dunlap
2008-06-30 18:47 ` Ingo Molnar
2008-07-01 0:34 ` Stephen Rothwell
2008-06-30 18:38 ` Jens Axboe
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=20080630183337.GD32211@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=randy.dunlap@oracle.com \
--cc=tglx@linutronix.de \
/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).