From: David Mosberger <davidm@napali.hpl.hp.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus <torvalds@transmeta.com>,
LKML <linux-kernel@vger.kernel.org>,
Trivial Kernel Patches <trivial@rustcorp.com.au>
Subject: Re: [PATCH] dup_task_struct can be static
Date: Wed, 19 Jun 2002 23:18:46 -0700 [thread overview]
Message-ID: <15633.29638.375426.808878@napali.hpl.hp.com> (raw)
In-Reply-To: <20020620121813.4d1e075f.sfr@canb.auug.org.au>
>>>>> On Thu, 20 Jun 2002 12:18:13 +1000, Stephen Rothwell <sfr@canb.auug.org.au> said:
Stephen> Hi Linus,
Stephen> [There may be lots of these depending on how bored I get :-)]
Stephen> dup_task_struct is defined and used only in kernel/fork.c.
Stephen> [This is not quite true, as arch/ia64/kernel/process.c also
Stephen> defines a global dup_task_struct function, but I don't know
Stephen> how it could ever be called.]
It does---once you apply a small patch by David Howells which hasn't
made it into Linus' tree yet.
--david
prev parent reply other threads:[~2002-06-20 6:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-20 2:18 Stephen Rothwell
2002-06-20 6:18 ` David Mosberger [this message]
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=15633.29638.375426.808878@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=davidm@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@transmeta.com \
--cc=trivial@rustcorp.com.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
all inboxes | Powered by JetHome®