From: James Morris <jmorris@namei.org>
To: David Howells <dhowells@redhat.com>
Cc: Thomas Meyer <thomas@m3y3r.de>, Adrian Bunk <bunk@kernel.org>,
Linux-Kernel <linux-kernel@vger.kernel.org>,
Linux-Next <linux-next@vger.kernel.org>
Subject: Re: next-20080808: bash: fork: Resource temporarily unavailable
Date: Sat, 9 Aug 2008 08:48:39 +1000 (EST) [thread overview]
Message-ID: <alpine.LRH.1.10.0808090847530.29741@tundra.namei.org> (raw)
In-Reply-To: <17923.1218234735@redhat.com>
On Fri, 8 Aug 2008, David Howells wrote:
>
> Adrian Bunk <bunk@kernel.org> wrote:
>
> > The only commits that touched kernel/fork.c between next-20080807 and
> > next-20080808 are David's CRED patches.
> >
> > David, can you look at this?
>
> I can, but I'll need a config file as it boots fine for me and passes the LTP
> testsuites I've run on it.
Is this with linux-next or my tree?
(I'm currently building next-20080808 & will do some testing).
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2008-08-08 22:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 17:02 Thomas Meyer
2008-08-08 17:21 ` Adrian Bunk
2008-08-08 21:48 ` James Morris
2008-08-09 8:44 ` jasper
2008-08-09 8:46 ` jasper
2008-08-09 11:26 ` Thomas Meyer
2008-08-09 12:52 ` David Howells
2008-08-09 13:11 ` Thomas Meyer
2008-08-09 14:07 ` David Howells
2008-08-09 22:55 ` Jasper Bryant-Greene
2008-08-10 9:45 ` David Howells
2008-08-10 10:30 ` Grant Wilson
2008-08-10 11:31 ` David Howells
2008-08-11 0:26 ` James Morris
2008-08-11 0:21 ` David Howells
2008-08-11 0:44 ` James Morris
2008-08-08 22:32 ` David Howells
2008-08-08 22:48 ` James Morris [this message]
2008-08-08 23:23 ` David Howells
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=alpine.LRH.1.10.0808090847530.29741@tundra.namei.org \
--to=jmorris@namei.org \
--cc=bunk@kernel.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=thomas@m3y3r.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
all inboxes | Powered by JetHome®