From: Matthew Wilcox <matthew@wil.cx>
To: Jaswinder Singh <jaswinder@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
kernelnewbies <kernelnewbies@nl.linux.org>,
David Woodhouse <dwmw2@infradead.org>,
tony.luck@intel.com, linux-ia64@vger.kernel.org
Subject: Re: [PATCH 9/22] ia64: Introducing asm/syscalls.h
Date: Mon, 21 Jul 2008 00:19:09 +0000 [thread overview]
Message-ID: <20080721001909.GA24246@parisc-linux.org> (raw)
In-Reply-To: <1216596835.3679.117.camel@jaswinder.satnam>
On Mon, Jul 21, 2008 at 05:03:55AM +0530, Jaswinder Singh wrote:
> Declaring arch-dependent syscalls for ia64 architecture
> +#ifndef CONFIG_PCI
> +asmlinkage long sys_pciconfig_read(unsigned long, unsigned long,
> + unsigned long, unsigned long, void *);
> +asmlinkage long sys_pciconfig_write(unsigned long, unsigned long,
> + unsigned long, unsigned long, void *);
> +#endif /* CONFIG_PCI */
These are already declared in linux/syscalls.h
And frankly, we should just make these return -ENOSYS always. Any
software that uses them is stuffed on machines with multiple domains.
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2008-07-21 0:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1216592500.3679.14.camel@jaswinder.satnam>
[not found] ` <1216592798.3679.22.camel@jaswinder.satnam>
[not found] ` <1216592879.3679.24.camel@jaswinder.satnam>
[not found] ` <1216593035.3679.27.camel@jaswinder.satnam>
[not found] ` <1216596035.3679.95.camel@jaswinder.satnam>
[not found] ` <1216596106.3679.98.camel@jaswinder.satnam>
[not found] ` <1216596325.3679.104.camel@jaswinder.satnam>
[not found] ` <1216596669.3679.112.camel@jaswinder.satnam>
[not found] ` <1216596749.3679.115.camel@jaswinder.satnam>
2008-07-20 23:45 ` [PATCH 9/22] ia64: Introducing asm/syscalls.h Jaswinder Singh
2008-07-21 0:19 ` Matthew Wilcox [this message]
2008-07-21 5:31 ` Jaswinder Singh
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=20080721001909.GA24246@parisc-linux.org \
--to=matthew@wil.cx \
--cc=dwmw2@infradead.org \
--cc=jaswinder@infradead.org \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
/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