From: Robert Love <rml@tech9.net>
To: Chris Wright <chris@wirex.com>
Cc: Daniel Jacobowitz <dan@debian.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Re: Capabilities-related change in 2.5.40
Date: 02 Oct 2002 14:10:55 -0400 [thread overview]
Message-ID: <1033582255.24476.52.camel@phantasy> (raw)
In-Reply-To: <20021002094417.D26557@figure1.int.wirex.com>
On Wed, 2002-10-02 at 12:44, Chris Wright wrote:
> kernel/sched.c::static inline task_t *find_process_by_pid...
>
> Guess that won't work w/out more changes. Perhaps it's simpler/safer
> to be just be explicit in this case.
>From 2.5.40:
static inline task_t *find_process_by_pid(pid_t pid)
{
return pid ? find_task_by_pid(pid) : current;
}
should work :)
Robert Love
next prev parent reply other threads:[~2002-10-02 18:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 16:49 Capabilities-related change in 2.5.40 Daniel Jacobowitz
2002-10-01 20:45 ` Chris Wright
2002-10-01 21:12 ` Daniel Jacobowitz
2002-10-02 7:38 ` [PATCH] " Chris Wright
2002-10-02 13:23 ` Daniel Jacobowitz
2002-10-02 14:33 ` Robert Love
2002-10-02 16:44 ` Chris Wright
2002-10-02 18:10 ` Robert Love [this message]
2002-10-02 18:21 ` Chris Wright
2002-10-02 16:25 ` Chris Wright
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=1033582255.24476.52.camel@phantasy \
--to=rml@tech9.net \
--cc=chris@wirex.com \
--cc=dan@debian.org \
--cc=linux-kernel@vger.kernel.org \
/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