[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v1 1/1] s390x: css: report errors from ccw_dstream_read/write
From: |
Cornelia Huck |
Subject: |
Re: [PATCH v1 1/1] s390x: css: report errors from ccw_dstream_read/write |
Date: |
Thu, 8 Apr 2021 15:26:14 +0200 |
On Thu, 8 Apr 2021 14:39:59 +0200
Halil Pasic <pasic@linux.ibm.com> wrote:
> On Thu, 8 Apr 2021 11:02:32 +0200
> Cornelia Huck <cohuck@redhat.com> wrote:
>
> > 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.
>
> With old releases, I wanted to say any QEMU that is still supported by
> us ;). For upstream it is backport to the stable versions currently in
> support.
>
> The commit message does not tell us if this is an enhancement or a
> bugfix, stable is not mentioned, and neither do we get the information
> since when is this problem existent. I simply wanted to have that
> discussion.
>
> Would it make sense to split this up into a virtio-ccw a css and a 3270
> patch? That way if there was a problem with let's say 3270, we could
> still keep the other two?
I'm not sure that makes sense; it's not too complicated.
- Re: [PATCH v1 1/1] s390x: css: report errors from ccw_dstream_read/write, (continued)
Re: [PATCH v1 1/1] s390x: css: report errors from ccw_dstream_read/write, Halil Pasic, 2021/04/07
Re: [PATCH v1 1/1] s390x: css: report errors from ccw_dstream_read/write, Halil Pasic, 2021/04/08
Re: [PATCH v1 1/1] s390x: css: report errors from ccw_dstream_read/write,
Cornelia Huck <=