public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Tommy Reynolds <reynolds@redhat.com>
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com
Subject: Re: compiler warnings and syscall macros
Date: Tue, 23 Sep 2003 10:23:24 -0400	[thread overview]
Message-ID: <3F70575C.2090707@nortelnetworks.com> (raw)
In-Reply-To: 20030922165104.29176e94.reynolds@redhat.com

Tommy Reynolds wrote:

> Why not do the obvious:
> 
> 	__sc_ret = -1UL;
> 
> and use a proper constant?


Cause I'm not thinking straight?

Chris


-- 
Chris Friesen                    | MailStop: 043/33/F10
Nortel Networks                  | work: (613) 765-0557
3500 Carling Avenue              | fax:  (613) 765-2986
Nepean, ON K2H 8E9 Canada        | email: cfriesen@nortelnetworks.com


  reply	other threads:[~2003-09-23 14:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-22 21:35 compiler warnings and syscall macros Chris Friesen
2003-09-22 21:51 ` Tommy Reynolds
2003-09-23 14:23   ` Chris Friesen [this message]
2003-09-22 22:49 ` H. Peter Anvin
2003-09-22 22:49 ` H. Peter Anvin
2003-09-22 23:08   ` H. Peter Anvin

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=3F70575C.2090707@nortelnetworks.com \
    --to=cfriesen@nortelnetworks.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reynolds@redhat.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