From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: kevin.tian@intel.com, George.Dunlap@eu.citrix.com, tim@xen.org,
eddie.dong@intel.com, keir.xen@gmail.com, jun.nakajima@intel.com,
xen-devel@lists.xenproject.org
Subject: Re: [V2 PATCH 0/3]: Fixup error codes in some p2m paths.
Date: Thu, 10 Apr 2014 15:04:17 -0700 [thread overview]
Message-ID: <20140410150417.07bd7c8d@mantra.us.oracle.com> (raw)
In-Reply-To: <53465D14020000780000778C@nat28.tlf.novell.com>
On Thu, 10 Apr 2014 07:57:56 +0100
"Jan Beulich" <JBeulich@suse.com> wrote:
> >>> On 10.04.14 at 02:18, <mukesh.rathor@oracle.com> wrote:
> > In reference to our discussion on propogating error codes here
> > http://osdir.com/ml/general/2014-04/msg13083.html
> >
> > please find v2 patches. Built on c/s: ac0f56a.
>
> No information here or in the individual patches as to what changed
> from v1?
>
> Jan
>
Chagnes in V2:
Patch 1:
- also rename p2m_pt_gfn_to_mfn to p2m_pt_get_entry
and p2m_pt_change_type_global to p2m_pt_change_entry_type_global.
Patch 2: No change
Patch 3:
- split if ( (rc = f()) to two lines
- fix interation to say iteration
- change EPERM to EIO
- fix logic in arch_do_domctl() to make it functionally same as it has
been
Mukesh
next prev parent reply other threads:[~2014-04-10 22:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 0:18 [V2 PATCH 0/3]: Fixup error codes in some p2m paths Mukesh Rathor
2014-04-10 0:19 ` [V2 PATCH 1/3] Rename public functions in p2m-pt.c Mukesh Rathor
2014-04-10 0:19 ` [V2 PATCH 2/3] Rename "set_p2m_entry" to "p2m_set_entry" Mukesh Rathor
2014-04-10 0:19 ` [V2 PATCH 3/3] P2M error code propogation Mukesh Rathor
2014-04-10 7:23 ` Jan Beulich
2014-04-10 6:57 ` [V2 PATCH 0/3]: Fixup error codes in some p2m paths Jan Beulich
2014-04-10 22:04 ` Mukesh Rathor [this message]
2014-04-13 20:43 ` Tim Deegan
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=20140410150417.07bd7c8d@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=eddie.dong@intel.com \
--cc=jun.nakajima@intel.com \
--cc=keir.xen@gmail.com \
--cc=kevin.tian@intel.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xenproject.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).