All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	Carsten Otte <cotte@de.ibm.com>, Alexander Graf <agraf@suse.de>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	KVM <kvm@vger.kernel.org>,
	linux-s390 <linux-s390@vger.kernel.org>
Subject: Re: [PATCH] KVM: s390: virtio-ccw bugfix.
Date: Thu, 4 Apr 2013 12:00:05 +0300	[thread overview]
Message-ID: <20130404090005.GA17411@redhat.com> (raw)
In-Reply-To: <20130404103554.03b81d3c@gondolin>

On Thu, Apr 04, 2013 at 10:35:54AM +0200, Cornelia Huck wrote:
> On Thu, 4 Apr 2013 11:27:39 +0300
> Gleb Natapov <gleb@redhat.com> wrote:
> 
> > On Thu, Apr 04, 2013 at 10:25:05AM +0200, Cornelia Huck wrote:
> > > Hi,
> > > 
> > > another virtio-ccw bugfix for a problem where we would not reset
> > > old I/O errors. Please apply.
> > > 
> > > Cornelia Huck (1):
> > >   KVM: s390: virtio_ccw: reset errors for new I/O.
> > > 
> > >  drivers/s390/kvm/virtio_ccw.c | 5 ++++-
> > >  1 file changed, 4 insertions(+), 1 deletion(-)
> > > 
> > Is this for 3.9 or 3.10?
> 
> I created the patch on top of kvm/queue (the problem won't surface with
> the current code, I only noticed it when I was mucking around with some
> experimental stuff).
Applied to queue. Thanks.

--
			Gleb.

      reply	other threads:[~2013-04-04  9:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04  8:25 [PATCH] KVM: s390: virtio-ccw bugfix Cornelia Huck
2013-04-04  8:25 ` [PATCH] KVM: s390: virtio_ccw: reset errors for new I/O Cornelia Huck
2013-04-04  9:28   ` Alexander Graf
2013-04-04 10:20     ` Cornelia Huck
2013-04-04 11:34       ` Alexander Graf
2013-04-04  8:27 ` [PATCH] KVM: s390: virtio-ccw bugfix Gleb Natapov
2013-04-04  8:35   ` Cornelia Huck
2013-04-04  9:00     ` Gleb Natapov [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=20130404090005.GA17411@redhat.com \
    --to=gleb@redhat.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=cotte@de.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=schwidefsky@de.ibm.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.