mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Ian Pratt <Ian.Pratt@xensource.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Xen-devel <xen-devel@lists.xensource.com>,
	virtualization <virtualization@lists.osdl.org>,
	Chris Wright <chrisw@sous-sol.org>
Subject: Re: [RFC PATCH 23/35] Increase x86 interrupt vector range
Date: Sun, 14 May 2006 08:52:24 +0100	[thread overview]
Message-ID: <96b6a9b036fc030017549f3446a13aab@cl.cam.ac.uk> (raw)
In-Reply-To: <200605131346_MC3-1-BFAF-FA0A@compuserve.com>


On 13 May 2006, at 18:44, Chuck Ebbert wrote:

> AFAIC this could go in anytime.  It's simple, self-contained and makes
> sense even without Xen.
>
> One minor nit: the IRQ value isn't negated, it's complemented.  The
> comments need to be fixed.

If we really want it disambiguated then we should call it something 
like 'bitwise-negated' or 'ones-complemented'. 'Complemented' alone is 
worse than 'negated' imo, since negation is at least the usual name for 
the tilde operator in C while complementation is an ambiguous term 
unless you know the base/radix.

  -- Keir


  reply	other threads:[~2006-05-14  7:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-13 17:44 Chuck Ebbert
2006-05-14  7:52 ` Keir Fraser [this message]
2006-05-14 17:08   ` Ingo Oeser
2006-05-15 21:57 ` Chris Wright
  -- strict thread matches above, loose matches on Subject: below --
2006-05-09  8:49 [RFC PATCH 00/35] Xen i386 paravirtualization support Chris Wright
2006-05-09  7:00 ` [RFC PATCH 23/35] Increase x86 interrupt vector range Chris Wright

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=96b6a9b036fc030017549f3446a13aab@cl.cam.ac.uk \
    --to=keir.fraser@cl.cam.ac.uk \
    --cc=76306.1226@compuserve.com \
    --cc=Ian.Pratt@xensource.com \
    --cc=chrisw@sous-sol.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.osdl.org \
    --cc=xen-devel@lists.xensource.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

all inboxes | Powered by JetHome®