All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, borntraeger@de.ibm.com, agraf@suse.de,
	rth@twiddle.net, pasic@linux.vnet.ibm.com,
	pmorel@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH v3 0/2] ERC cleanup and CRW bugfix
Date: Thu, 3 Aug 2017 10:25:22 +0200	[thread overview]
Message-ID: <20170803102522.4758f156@gondolin> (raw)
In-Reply-To: <20170803003527.86979-1-bjsdjshi@linux.vnet.ibm.com>

On Thu,  3 Aug 2017 02:35:25 +0200
Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com> wrote:

> This series is trying to:
> 1. clear up ERC related code
> 2. bugfix for channel path related CRW generation
> 
> Change log
> ----------
> v2->v3:
> Added Halil's R-B on both patches.
> Patch #1:
>   Added ERC "installed parameters restored".
> 
> v1->v2:
> Patch #1:
>   Add all ERCs.
>   Commit message update.
> Patch #2:
>   Rename the new added parameter to more speaking name -- solicited.
> 
> Dong Jia Shi (2):
>   s390x/css: use macro for event-information pending error recover code
>   s390x/css: generate solicited crw for rchp completion signaling
> 
>  hw/s390x/css.c            | 16 ++++++++++------
>  include/hw/s390x/css.h    |  3 ++-
>  include/hw/s390x/ioinst.h | 12 ++++++++++--
>  3 files changed, 22 insertions(+), 9 deletions(-)
> 

Thanks, applied.

      parent reply	other threads:[~2017-08-03  8:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-03  0:35 [Qemu-devel] [PATCH v3 0/2] ERC cleanup and CRW bugfix Dong Jia Shi
2017-08-03  0:35 ` [Qemu-devel] [PATCH v3 1/2] s390x/css: use macro for event-information pending error recover code Dong Jia Shi
2017-08-03  0:35 ` [Qemu-devel] [PATCH v3 2/2] s390x/css: generate solicited crw for rchp completion signaling Dong Jia Shi
2017-08-03  8:25 ` Cornelia Huck [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=20170803102522.4758f156@gondolin \
    --to=cohuck@redhat.com \
    --cc=agraf@suse.de \
    --cc=bjsdjshi@linux.vnet.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=pasic@linux.vnet.ibm.com \
    --cc=pmorel@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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.