From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: missing entries in fsys.S
Date: Wed, 15 Feb 2006 16:15:44 +0000 [thread overview]
Message-ID: <200602151615.k1FGFjg07648@unix-os.sc.intel.com> (raw)
In-Reply-To: <20060215143359.GB14787@frankl.hpl.hp.com>
Stephane Eranian wrote on Wednesday, February 15, 2006 6:34 AM
> It appears that Linus's 2.6 git tree is missing some entryies in fsys.S.
> I don't know abot your particular GIT tree. In any case, here is a patch
> to fix this.
That's what the .space directive is for when I added it a couple of weeks
ago. It automatically fills in zero so lazy people like me can save a few
key strokes. I guess the name __NR_syscall_last is not intuitive, it meant
to be last_non_zero entry for fsys table.
- Ken
See this posting:
http://www.gelato.unsw.edu.au/archives/linux-ia64/0602/16862.html
next prev parent reply other threads:[~2006-02-15 16:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 14:33 missing entries in fsys.S Stephane Eranian
2006-02-15 16:15 ` Chen, Kenneth W [this message]
2006-02-15 16:28 ` Stephane Eranian
2006-02-15 19:16 ` Chen, Kenneth W
2006-02-15 19:40 ` Luck, Tony
2006-02-15 19:58 ` Chen, Kenneth W
2006-02-15 20:04 ` Luck, Tony
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=200602151615.k1FGFjg07648@unix-os.sc.intel.com \
--to=kenneth.w.chen@intel.com \
--cc=linux-ia64@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