From: "Randy.Dunlap" <rddunlap@osdl.org>
To: davidsen@tmr.com (bill davidsen)
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Fastboot] kexec update (2.6.0-test7)
Date: Thu, 9 Oct 2003 18:33:46 -0700 [thread overview]
Message-ID: <20031009183346.3ae74277.rddunlap@osdl.org> (raw)
In-Reply-To: <bm4js7$6db$1@gatekeeper.tmr.com>
On 9 Oct 2003 21:27:35 GMT davidsen@tmr.com (bill davidsen) wrote:
| In article <m1y8vufe5l.fsf@ebiederm.dsl.xmission.com>,
| Eric W. Biederman <ebiederm@xmission.com> wrote:
| | Cherry George Mathew <cherry@sdf.lonestar.org> writes:
| |
| | > On Wed, 8 Oct 2003, Randy.Dunlap wrote:
| | >
| | > > You'll need to update the kexec-syscall.c file for the correct
| | > > kexec syscall number (274).
| | >
| | > Is there a consensus about what the syscall number will finally be ? We've
| | > jumped from 256 to 274 over the 2.5.x+ series kernels. Or is it the law
| | > the Jungle ?
| |
| | So far the law of the jungle. Regardless of the rest it looks like it
| | is time to submit a place keeping patch.
|
| Forgive me if the politics of this have changed, but will a place
| keeping patch be accepted for a feature which has not?
Like the one recently added for "vserver" ??
#define __NR_vserver 273
and
.long sys_ni_syscall /* sys_vserver */
(ni == not implemented)
But I don't think that it's quite time for a placeholder syscall number
(IMO of course). Eric can submit one though.
--
~Randy
next prev parent reply other threads:[~2003-10-10 1:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 0:22 Randy.Dunlap
2003-10-09 4:04 ` [Fastboot] " Cherry George Mathew
2003-10-09 18:40 ` Eric W. Biederman
2003-10-09 21:02 ` Bill Davidsen
2003-10-09 21:18 ` Steven Cole
2003-10-09 21:27 ` bill davidsen
2003-10-10 1:33 ` Randy.Dunlap [this message]
2003-10-11 13:57 ` Bill Davidsen
2003-10-11 16:49 ` Randy.Dunlap
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=20031009183346.3ae74277.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=davidsen@tmr.com \
--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
all inboxes | Powered by JetHome®