From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] IRQ Cleanup: rename nr_ioapic_registers to nr_ioapic_entries
Date: Mon, 26 Sep 2011 09:25:22 -0700 [thread overview]
Message-ID: <CAA5F582.217CD%keir.xen@gmail.com> (raw)
In-Reply-To: <4E80B8F90200007800057DCE@nat28.tlf.novell.com>
On 26/09/2011 08:40, "Jan Beulich" <JBeulich@suse.com> wrote:
>> I guess it depends on whether you consider that we should stay in line
>> with Linux or not. While the code did start in Linux, it has diverged
>> so far that it really is its own file now.
>>
>> Either we should un-diverge from Linux (unlikely to happen), or consider
>> it properly forked and not worry; staying in this intermediate state is
>> not sustainable and leads to keeping misleading bits about while an
>> overhaul is needed.
>
> There's one more alternative: You could propose the same renaming
> on Linux.
Not a bad idea. But I don't think it should stop us making these kinds of
changes in Xen now. We stayed in sync with upstream Linux on these files for
a long while, but we're well diverged now.
-- Keir
next prev parent reply other threads:[~2011-09-26 16:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 14:48 [PATCH] IRQ Cleanup: rename nr_ioapic_registers to nr_ioapic_entries Andrew Cooper
2011-09-26 14:57 ` Jan Beulich
2011-09-26 15:15 ` Andrew Cooper
2011-09-26 15:40 ` Jan Beulich
2011-09-26 16:25 ` Keir Fraser [this message]
2011-09-26 15:45 ` Konrad Rzeszutek Wilk
2011-09-26 16:27 ` Keir Fraser
2011-09-26 17:04 ` Dan Magenheimer
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=CAA5F582.217CD%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.