From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Carlos O'Donell <carlos@systemhalted.org>
Cc: Andreas Jaeger <aj@suse.com>,
"libc-ports@sourceware.org" <libc-ports@sourceware.org>
Subject: Re: Convert HPPA to use <bits/fcntl-linux.h>
Date: Fri, 26 Oct 2012 01:11:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1210260110090.30538@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAE2sS1gk_2qphnj0OTqTxjWKuM=YB8eqEPknQXdn7nrXs+RAww@mail.gmail.com>
On Thu, 25 Oct 2012, Carlos O'Donell wrote:
> I've compared it to the upstream kernel.
Did this include checking whether the generic O_PATH value is correct for
HPPA (the absence of O_PATH from hppa/bits/fcntl.h being point (j) in my
list of ways the port was out of date)?
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2012-10-26 1:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 19:07 Andreas Jaeger
2012-10-26 1:05 ` Carlos O'Donell
2012-10-26 1:11 ` Joseph S. Myers [this message]
2012-10-26 15:29 ` Carlos O'Donell
2012-10-26 19:17 ` Andreas Jaeger
2012-10-26 19:41 ` Carlos O'Donell
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=Pine.LNX.4.64.1210260110090.30538@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=aj@suse.com \
--cc=carlos@systemhalted.org \
--cc=libc-ports@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).