From: Felix Janda <felix.janda@posteo.de>
To: linux-pci@vger.kernel.org
Subject: [PATCH pciutils] pread.h: Remove support for libc5
Date: Sun, 29 Mar 2015 09:59:32 +0100 [thread overview]
Message-ID: <20150329085931.GA8259@euler> (raw)
The support code for libc5 breaks building on linux i386 with
other libcs that don't define __GLIBC__.
---
lib/pread.h | 9 ---------
1 file changed, 9 deletions(-)
diff --git a/lib/pread.h b/lib/pread.h
index 0e64326..3db90e3 100644
--- a/lib/pread.h
+++ b/lib/pread.h
@@ -30,15 +30,6 @@ static int pread(unsigned int fd, void *buf, size_t size, loff_t where)
static int pwrite(unsigned int fd, void *buf, size_t size, loff_t where)
{ return syscall(SYS_pwrite, fd, buf, size, where); }
-#elif defined(i386)
-/* old libc on i386 -> call syscalls directly the old way */
-#include <asm/unistd.h>
-static _syscall5(int, pread, unsigned int, fd, void *, buf, size_t, size, u32, where_lo, u32, where_hi);
-static _syscall5(int, pwrite, unsigned int, fd, void *, buf, size_t, size, u32, where_lo, u32, where_hi);
-static int do_read(struct pci_dev *d UNUSED, int fd, void *buf, size_t size, int where) { return pread(fd, buf, size, where, 0); }
-static int do_write(struct pci_dev *d UNUSED, int fd, void *buf, size_t size, int where) { return pwrite(fd, buf, size, where, 0); }
-#define PCI_HAVE_DO_READ
-
#else
/* In all other cases we use lseek/read/write instead to be safe */
#define make_rw_glue(op) \
--
2.0.5
next reply other threads:[~2015-03-29 9:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-29 8:59 Felix Janda [this message]
2015-04-09 14:37 ` [PATCH pciutils] pread.h: Remove support for libc5 Martin Mares
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=20150329085931.GA8259@euler \
--to=felix.janda@posteo.de \
--cc=linux-pci@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;
as well as URLs for NNTP newsgroup(s).