Displaying 20 results from an estimated 7000 matches similar to: "[PULL 0/1] virtio-ccw: one more patch for 4.21"
2019 Jan 03
2
[PULL 0/1] virtio-ccw: one more patch for 4.21
On Thu, Jan 03, 2019 at 09:55:07AM +0100, Cornelia Huck wrote:
> On Wed, 19 Dec 2018 11:14:13 +0100
> Cornelia Huck <cohuck at redhat.com> wrote:
>
> > The following changes since commit 37d1246af2d530710cf5822d2845774f01c03b22:
> >
> > virtio_net: bulk free tx skbs (2018-12-06 14:28:39 -0500)
> >
> > are available in the Git repository at:
>
2019 Jan 03
2
[PULL 0/1] virtio-ccw: one more patch for 4.21
On Thu, Jan 03, 2019 at 09:55:07AM +0100, Cornelia Huck wrote:
> On Wed, 19 Dec 2018 11:14:13 +0100
> Cornelia Huck <cohuck at redhat.com> wrote:
>
> > The following changes since commit 37d1246af2d530710cf5822d2845774f01c03b22:
> >
> > virtio_net: bulk free tx skbs (2018-12-06 14:28:39 -0500)
> >
> > are available in the Git repository at:
>
2018 Dec 18
1
[PATCH] virtio-ccw: diag 500 may return a negative cookie
If something goes wrong in the kvm io bus handling, the virtio-ccw
diagnose may return a negative error value in the cookie gpr.
Document this.
Signed-off-by: Cornelia Huck <cohuck at redhat.com>
---
Even if the virtio spec is the correct place to specify what diag 500
subcode 3 does, we also should mention here that the cookie may be
an error.
---
2019 Jan 03
0
[PULL 0/1] virtio-ccw: one more patch for 4.21
On Wed, 19 Dec 2018 11:14:13 +0100
Cornelia Huck <cohuck at redhat.com> wrote:
> The following changes since commit 37d1246af2d530710cf5822d2845774f01c03b22:
>
> virtio_net: bulk free tx skbs (2018-12-06 14:28:39 -0500)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git tags/virtio-ccw-20181219
>
2019 Jan 03
0
[PULL 0/1] virtio-ccw: one more patch for 4.21
On Thu, Jan 03, 2019 at 11:50:22AM -0500, Michael S. Tsirkin wrote:
> On Thu, Jan 03, 2019 at 09:55:07AM +0100, Cornelia Huck wrote:
> > On Wed, 19 Dec 2018 11:14:13 +0100
> > Cornelia Huck <cohuck at redhat.com> wrote:
> >
> > > The following changes since commit 37d1246af2d530710cf5822d2845774f01c03b22:
> > >
> > > virtio_net: bulk free
2018 Sep 26
4
[PULL 0/2] virtio-ccw fixes
The following changes since commit 8c0f9f5b309d627182d5da72a69246f58bde1026:
Revert "uapi/linux/keyctl.h: don't use C++ reserved keyword as a struct member name" (2018-09-25 13:28:58 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git tags/virtio-ccw-20180926
for you to fetch changes up to
2018 Dec 06
1
[PULL 0/2] virtio-ccw fixes
On Thu, 29 Nov 2018 15:56:48 +0100
Cornelia Huck <cohuck at redhat.com> wrote:
> On Wed, 26 Sep 2018 18:48:28 +0200
> Cornelia Huck <cohuck at redhat.com> wrote:
>
> > The following changes since commit 8c0f9f5b309d627182d5da72a69246f58bde1026:
> >
> > Revert "uapi/linux/keyctl.h: don't use C++ reserved keyword as a struct member name"
2017 Dec 14
2
[PULL 0/1] s390/virtio update
The following changes since commit e073f74a5a39c6dc45f28a5006c21aa94490d9b8:
Merge branch 'this' into vhost (2017-12-07 18:39:24 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git tags/virtio-s390-20171214
for you to fetch changes up to 619b4b0ba832144d4be899640a2047f9675df849:
virtio/s390: implement PM operations for
2017 Dec 14
2
[PULL 0/1] s390/virtio update
The following changes since commit e073f74a5a39c6dc45f28a5006c21aa94490d9b8:
Merge branch 'this' into vhost (2017-12-07 18:39:24 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git tags/virtio-s390-20171214
for you to fetch changes up to 619b4b0ba832144d4be899640a2047f9675df849:
virtio/s390: implement PM operations for
2017 Jul 04
4
[PATCH 0/1] Change email address
New employer, new address. Make sure people use the right one.
Christian, Martin, it's probably quickest if one of you takes this.
Cornelia Huck (1):
Update my email address
MAINTAINERS | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--
2.13.0
2017 Jul 04
4
[PATCH 0/1] Change email address
New employer, new address. Make sure people use the right one.
Christian, Martin, it's probably quickest if one of you takes this.
Cornelia Huck (1):
Update my email address
MAINTAINERS | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--
2.13.0
2017 Jan 16
7
[PULL 0/5] virtio/s390 patches for -next
Michael,
the following patches have all been posted in the past. I've
collected them on top of your vhost branch -- please let me
know whether this works for you.
The following changes since commit 6bdf1e0efb04a1716373646cb6f35b73addca492:
Makefile: drop -D__CHECK_ENDIAN__ from cflags (2016-12-16 00:13:43 +0200)
are available in the git repository at:
2017 Jan 16
7
[PULL 0/5] virtio/s390 patches for -next
Michael,
the following patches have all been posted in the past. I've
collected them on top of your vhost branch -- please let me
know whether this works for you.
The following changes since commit 6bdf1e0efb04a1716373646cb6f35b73addca492:
Makefile: drop -D__CHECK_ENDIAN__ from cflags (2016-12-16 00:13:43 +0200)
are available in the git repository at:
2018 Nov 29
0
[PULL 0/2] virtio-ccw fixes
On Wed, 26 Sep 2018 18:48:28 +0200
Cornelia Huck <cohuck at redhat.com> wrote:
> The following changes since commit 8c0f9f5b309d627182d5da72a69246f58bde1026:
>
> Revert "uapi/linux/keyctl.h: don't use C++ reserved keyword as a struct member name" (2018-09-25 13:28:58 +0200)
>
> are available in the Git repository at:
>
>
2017 Nov 28
2
[PATCH v4] s390/virtio: add BSD license to virtio-ccw
The original intent of the virtio header relicensing
from 2008 was to make sure anyone can implement compatible
devices/drivers. The virtio-ccw was omitted by mistake.
We have an ack from the only contributor as well as the
maintainer from IBM, so it's not too late to fix that.
Make it dual-licensed with GPLv2, as the whole kernel is GPL2.
Acked-by: Christian Borntraeger <borntraeger at
2017 Nov 28
2
[PATCH v4] s390/virtio: add BSD license to virtio-ccw
The original intent of the virtio header relicensing
from 2008 was to make sure anyone can implement compatible
devices/drivers. The virtio-ccw was omitted by mistake.
We have an ack from the only contributor as well as the
maintainer from IBM, so it's not too late to fix that.
Make it dual-licensed with GPLv2, as the whole kernel is GPL2.
Acked-by: Christian Borntraeger <borntraeger at
2017 Nov 10
2
[PATCH] MAINTAINERS: add virtio-ccw.h to virtio/s390 section
The file arch/s390/include/uapi/asm/virtio-ccw.h belongs to the
s390 virtio drivers as well.
Signed-off-by: Cornelia Huck <cohuck at redhat.com>
---
Martin, Heiko: It's probably best to take this through your tree.
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 6671f375f7fc..48c6f1179b9b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
2017 Nov 10
2
[PATCH] MAINTAINERS: add virtio-ccw.h to virtio/s390 section
The file arch/s390/include/uapi/asm/virtio-ccw.h belongs to the
s390 virtio drivers as well.
Signed-off-by: Cornelia Huck <cohuck at redhat.com>
---
Martin, Heiko: It's probably best to take this through your tree.
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 6671f375f7fc..48c6f1179b9b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
2019 Jun 03
2
[PATCH v3 7/8] virtio/s390: use DMA memory for ccw I/O and classic notifiers
On Wed, 29 May 2019 14:26:56 +0200
Michael Mueller <mimu at linux.ibm.com> wrote:
> From: Halil Pasic <pasic at linux.ibm.com>
>
> Before virtio-ccw could get away with not using DMA API for the pieces of
> memory it does ccw I/O with. With protected virtualization this has to
> change, since the hypervisor needs to read and sometimes also write these
> pieces of
2019 Jun 03
2
[PATCH v3 7/8] virtio/s390: use DMA memory for ccw I/O and classic notifiers
On Wed, 29 May 2019 14:26:56 +0200
Michael Mueller <mimu at linux.ibm.com> wrote:
> From: Halil Pasic <pasic at linux.ibm.com>
>
> Before virtio-ccw could get away with not using DMA API for the pieces of
> memory it does ccw I/O with. With protected virtualization this has to
> change, since the hypervisor needs to read and sometimes also write these
> pieces of