From: Wei Liu <wei.liu2@citrix.com>
To: Paulina Szubarczyk <paulinaszubarczyk@gmail.com>
Cc: "Wei Liu" <wei.liu2@citrix.com>,
"Ian Campbell" <ian.campbell@citrix.com>,
George.Dunlap@eu.citrix.com,
"Dario Faggioli" <dario.faggioli@citrix.com>,
xen-devel@lists.xenproject.org,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH 00/11] Return failure on failure for more xl commands
Date: Thu, 31 Mar 2016 16:06:44 +0100 [thread overview]
Message-ID: <20160331150644.GL18437@citrix.com> (raw)
In-Reply-To: <CAMQpU2qBAovbY6Sd-7K9gsa7eJeVGObWUEodgB6A1aQWiHzUaQ@mail.gmail.com>
On Wed, Mar 30, 2016 at 07:19:41PM +0200, Paulina Szubarczyk wrote:
> Yes, I was looking at wrong branch, I am sorry. The patches
>
> * {01-04,08,11} were not attached in the previous patch [0].
>
> * {05,06} are applied in the version made by George Dunlap.
> I added the changes to return 0/1 in internal functions
> and EXIT_{SUCCESS/FAILURE} according to [2]. It certainly should be
> resend.
>
> * 07 was attached in the previous patch but is not applied in staging.
> It relates pci-* functions. I modified it as in the point higher.
>
> * 09 is applied.
>
> * 10 is not applied, I did not modified it. It brings coding style improvements.
>
Given that the applied patches interleave with not-yet-applied patches I
think it's best if you can rebase on top of staging and resend.
We shall look at it in due time. Note that we're currently quite busy so
it might take us some time to get to your patches. Do you have a
deadline that you need to meet? Deadline for OPW etc?
Wei.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-03-31 15:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 15:02 [PATCH 00/11] Return failure on failure for more xl commands Paulina Szubarczyk
2016-03-30 15:02 ` [PATCH 01/11] libxl_pci: improve return codes " Paulina Szubarczyk
2016-03-30 15:02 ` [PATCH 02/11] libxl_pci: clean an unused return variable Paulina Szubarczyk
2016-03-30 15:02 ` [PATCH 03/11] libxl_pci: Return error code for more pci-* functions Paulina Szubarczyk
2016-03-30 15:02 ` [PATCH 04/11] xl: improve return code for freemem function Paulina Szubarczyk
2016-03-30 15:02 ` [PATCH 05/11] xl: Make set_memory_target return an error code on failure Paulina Szubarczyk
2016-03-30 15:02 ` [PATCH 06/11] xl: Return an error on failed cd-insert Paulina Szubarczyk
2016-03-30 15:02 ` [PATCH 07/11] xl: Return error codes for pci* commands Paulina Szubarczyk
2016-03-30 15:02 ` [PATCH 08/11] xl: improve main_tmem_* return codes Paulina Szubarczyk
2016-03-30 15:02 ` [PATCH 09/11] libxl: Remove pointless hypercall from libxl_set_memory_target Paulina Szubarczyk
2016-03-30 15:02 ` [PATCH 10/11] libxl: Fix libxl_set_memory_target return value Paulina Szubarczyk
2016-03-30 15:02 ` [PATCH 11/11] libxl: libxl_tmem functions improving coding style Paulina Szubarczyk
2016-03-30 15:14 ` [PATCH 00/11] Return failure on failure for more xl commands Wei Liu
2016-03-30 17:19 ` Paulina Szubarczyk
2016-03-31 15:06 ` Wei Liu [this message]
2016-04-01 9:55 ` Paulina Szubarczyk
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=20160331150644.GL18437@citrix.com \
--to=wei.liu2@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=paulinaszubarczyk@gmail.com \
--cc=roger.pau@citrix.com \
--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).