All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: Tejus GK <tejus.gk@nutanix.com>
Cc: qemu-devel@nongnu.org,  peterx@redhat.com,  leobras@redhat.com,
	berrange@redhat.com,  shivam.kumar1@nutanix.com
Subject: Re: [RFC v3 0/2] migration: Update error description whenever migration fails
Date: Thu, 18 May 2023 13:53:55 +0200	[thread overview]
Message-ID: <87ednddfe4.fsf@secure.mitica> (raw)
In-Reply-To: <20230518062308.90631-1-tejus.gk@nutanix.com> (Tejus GK's message of "Thu, 18 May 2023 06:23:06 +0000")

Tejus GK <tejus.gk@nutanix.com> wrote:
> Hi everyone,
>
> Thank you everyone for the reviews, this is the	v3 patchset based on the 
> reviews	received on the	previous ones. 

Hi

I did the review-by.
But you have to resend with a proper PATCH subject line to get this in.

I will split the removal of the duplicated yank, because that is
independent of the patch.

And for the rest it is ok.

Thanks, Juan.


>
> Links to the previous patchsets:
> v1: https://lists.gnu.org/archive/html/qemu-devel/2023-05/msg00868.html
> v2: https://lists.gnu.org/archive/html/qemu-devel/2023-05/msg01943.html
>
> I've broken this patchset into two parts; the first patch contains fixes
> for places in migration.c where	the failure reason is not updated.
> Compared to the	previous patchset, this	fixes a	few errors existing in  
> the last patch and covers a few	more places where the failure reason 
> isn't updated. 
>
> The second patch, covers places	outside	of migration.c,	which eventually 
> lead to	a migration failure, along with	an error_report() call being 
> made, however without an update	for the failure	reason.	I am aware that	
> the changes in vmstate.c breaks	the build due to a unit-test build 
> failing, so I wanted to	know the right way to approach this. 
>
> regards,
> Tejus
>
>
> Tejus GK (2):
>   migration: Update error description whenever migration fails
>   migration: Update error description whenever migration fails
>
>  migration/migration.c | 23 ++++++++++++-----------
>  migration/savevm.c    | 13 ++++++++++---
>  migration/vmstate.c   | 13 ++++++++++---
>  3 files changed, 32 insertions(+), 17 deletions(-)



      parent reply	other threads:[~2023-05-18 11:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18  6:23 [RFC v3 0/2] migration: Update error description whenever migration fails Tejus GK
2023-05-18  6:23 ` [RFC v3 1/2] " Tejus GK
2023-05-18 11:50   ` Juan Quintela
2023-05-18 12:24   ` Daniel P. Berrangé
2023-05-18  6:23 ` [RFC v3 2/2] " Tejus GK
2023-05-18 11:52   ` Juan Quintela
2023-05-18 14:24     ` Tejus GK
2023-05-18 11:53 ` Juan Quintela [this message]

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=87ednddfe4.fsf@secure.mitica \
    --to=quintela@redhat.com \
    --cc=berrange@redhat.com \
    --cc=leobras@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=shivam.kumar1@nutanix.com \
    --cc=tejus.gk@nutanix.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.