From: Blaisorblade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
akpm@osdl.org, linux-kernel@vger.kernel.org, jdike@addtoit.com
Subject: Re: [uml-devel] Re: [patch 1/1] uml: fix some ptrace functions returns values
Date: Thu, 25 Nov 2004 05:14:46 +0100 [thread overview]
Message-ID: <200411250514.46355.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <41A3F6F6.1040903@osdl.org>
On Wednesday 24 November 2004 03:50, Randy.Dunlap wrote:
> blaisorblade_spam@yahoo.it wrote:
> > From: Jeff Dike <jdike@addtoit.com>
> >
> > This patch adds ptrace_setfpregs and makes these functions return -errno
> > on failure.
> Looks OK except that someone's SPACEBAR is broken (missing)
> and there are (unneeded/unwanted) parens on the returns.
Yes, that is Jeff Dike's keyboard - it's cursing all over arch/um with that
style.
I'm going to resend it more conforming to the kernel style.
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2004-11-25 5:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-24 0:07 [uml-devel] [patch 1/1] uml: fix some ptrace functions returns values blaisorblade_spam
2004-11-24 2:50 ` [uml-devel] " Randy.Dunlap
2004-11-25 4:14 ` Blaisorblade [this message]
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=200411250514.46355.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=akpm@osdl.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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