From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "konrad@kernel.org" <konrad@kernel.org>,
"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>,
Jan Beulich <jbeulich@suse.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Is: PVH + ARM new hypercalls. Was: Re: [PATCH]: PVH: specify xen features strings cleany for PVH
Date: Mon, 4 Feb 2013 17:04:49 -0800 [thread overview]
Message-ID: <20130204170449.24408e42@mantra.us.oracle.com> (raw)
In-Reply-To: <1359973901.5281.35.camel@zakaz.uk.xensource.com>
On Mon, 4 Feb 2013 10:31:41 +0000
Ian Campbell <Ian.Campbell@citrix.com> wrote:
> On Fri, 2013-02-01 at 19:27 +0000, Mukesh Rathor wrote:
> > On Fri, 01 Feb 2013 16:24:57 +0000
> > "Jan Beulich" <jbeulich@suse.com> wrote:
> >
> I don't much care about the gdt vs u naming for the union, although I
> would probably have gone with the more meaningful gdt if it were me.
> cscope-wise in emacs I would just use "C-c s t" to look for "gdt.size"
> etc.
Unf vim cscope doesn't support that. Moreover, I bet if size was accessed
via pointer, you couldn't search it that way either. In general, all
enterprise software I've worked on prohibited such generic names for
the reason people couldn't easily find their usages. I find it very
frustrating, and I hope I can continue to be able to read xen code.
Thanks,
Mukesh
next prev parent reply other threads:[~2013-02-05 1:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-19 1:35 [PATCH]: PVH: specify xen features strings cleany for PVH Mukesh Rathor
2013-01-21 12:06 ` Jan Beulich
2013-01-22 23:12 ` Mukesh Rathor
2013-01-23 8:22 ` Jan Beulich
2013-01-23 22:43 ` Mukesh Rathor
2013-01-24 9:16 ` Jan Beulich
2013-01-24 9:27 ` Ian Campbell
2013-01-24 15:10 ` Konrad Rzeszutek Wilk
2013-01-24 23:13 ` Mukesh Rathor
2013-01-25 8:02 ` Jan Beulich
2013-01-25 10:11 ` Ian Campbell
2013-01-25 10:27 ` Jan Beulich
2013-01-25 10:43 ` Ian Campbell
2013-01-28 16:26 ` Is: PVH + ARM new hypercalls. Was: " Konrad Rzeszutek Wilk
2013-01-29 2:57 ` Mukesh Rathor
2013-01-29 10:48 ` Jan Beulich
2013-02-01 2:23 ` Mukesh Rathor
2013-02-01 16:24 ` Jan Beulich
2013-02-01 19:27 ` Mukesh Rathor
2013-02-04 10:31 ` Ian Campbell
2013-02-05 1:04 ` Mukesh Rathor [this message]
2013-02-05 7:53 ` Jan Beulich
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=20130204170449.24408e42@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=jbeulich@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=konrad@kernel.org \
--cc=xen-devel@lists.xen.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 NNTP newsgroup(s).