From: Cornelia Huck <cohuck@redhat.com>
To: Halil Pasic <pasic@linux.ibm.com>
Cc: thuth@redhat.com, frankja@linux.ibm.com,
Pierre Morel <pmorel@linux.ibm.com>,
david@redhat.com, mst@redhat.com, richard.henderson@linaro.org,
qemu-devel@nongnu.org, borntraeger@de.ibm.com,
qemu-s390x@nongnu.org, pbonzini@redhat.com,
marcandre.lureau@redhat.com, imbrenda@linux.ibm.com
Subject: Re: [PATCH v1 1/1] s390x: css: report errors from ccw_dstream_read/write
Date: Thu, 8 Apr 2021 11:02:32 +0200 [thread overview]
Message-ID: <20210408110232.2bf02df4.cohuck@redhat.com> (raw)
In-Reply-To: <20210407194711.459176c3.pasic@linux.ibm.com>
On Wed, 7 Apr 2021 19:47:11 +0200
Halil Pasic <pasic@linux.ibm.com> wrote:
> So this begs the question, do we need this fixed for old releases as well?
>
> My answer is yes we do. Conny what do you think?
What do you mean with "old releases"? The dstream rework was in 2.11,
and I doubt that anyone is using anything older, or a downstream
release that is based on pre-2.11.
If you mean "include in stable", then yes, we can do that; if we want
the commit in 6.0, I need the final version soon.
next prev parent reply other threads:[~2021-04-08 9:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 7:44 [PATCH v1 0/1] s390x: css: report errors from ccw_dstream_read/write Pierre Morel
2021-04-06 7:44 ` [PATCH v1 1/1] " Pierre Morel
2021-04-06 15:03 ` Cornelia Huck
2021-04-07 11:41 ` Pierre Morel
2021-04-07 16:54 ` Halil Pasic
2021-04-08 8:53 ` Cornelia Huck
2021-04-07 17:47 ` Halil Pasic
2021-04-08 9:02 ` Cornelia Huck [this message]
2021-04-08 12:32 ` Pierre Morel
2021-04-08 13:23 ` Cornelia Huck
2021-04-08 16:18 ` Pierre Morel
2021-04-08 12:39 ` Halil Pasic
2021-04-08 13:26 ` Cornelia Huck
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=20210408110232.2bf02df4.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=pmorel@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.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.