From: Cornelia Huck <cohuck@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org,
Christian Borntraeger <borntraeger@de.ibm.com>,
Alexander Graf <agraf@suse.de>,
Farhan Ali <alifm@linux.vnet.ibm.com>,
David Hildenbrand <david@redhat.com>,
Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com>,
Alexey Kardashevskiy <aik@ozlabs.ru>
Subject: Re: [Qemu-devel] [PATCH v4 10/11] pc-bios/s390-ccw: Add virtio-net driver code
Date: Tue, 11 Jul 2017 16:32:28 +0200 [thread overview]
Message-ID: <20170711163228.651abd7f@dhcp-192-215.str.redhat.com> (raw)
In-Reply-To: <1499781397-19749-11-git-send-email-thuth@redhat.com>
On Tue, 11 Jul 2017 15:56:36 +0200
Thomas Huth <thuth@redhat.com> wrote:
> The driver provides the recv() and send() functions which will
> be required by SLOF's libnet code for receiving and sending
> packets.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> pc-bios/s390-ccw/netboot.mak | 2 +-
> pc-bios/s390-ccw/virtio-net.c | 135 ++++++++++++++++++++++++++++++++++++++++++
> pc-bios/s390-ccw/virtio.c | 5 ++
> pc-bios/s390-ccw/virtio.h | 12 +++-
> 4 files changed, 151 insertions(+), 3 deletions(-)
> create mode 100644 pc-bios/s390-ccw/virtio-net.c
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
next prev parent reply other threads:[~2017-07-11 14:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 13:56 [Qemu-devel] [PATCH v4 00/11] Implement network booting in the s390-ccw BIOS Thomas Huth
2017-07-11 13:56 ` [Qemu-devel] [PATCH v4 01/11] pc-bios/s390-ccw: Move libc functions to separate header Thomas Huth
2017-07-11 13:56 ` [Qemu-devel] [PATCH v4 02/11] pc-bios/s390-ccw: Move ebc2asc to sclp.c Thomas Huth
2017-07-11 13:56 ` [Qemu-devel] [PATCH v4 03/11] pc-bios/s390-ccw: Move virtio-block related functions into a separate file Thomas Huth
2017-07-11 13:56 ` [Qemu-devel] [PATCH v4 04/11] pc-bios/s390-ccw: Add a write() function for stdio Thomas Huth
2017-07-11 13:56 ` [Qemu-devel] [PATCH v4 05/11] pc-bios/s390-ccw: Move byteswap functions to a separate header Thomas Huth
2017-07-11 13:56 ` [Qemu-devel] [PATCH v4 06/11] pc-bios/s390-ccw: Remove unused structs from virtio.h Thomas Huth
2017-07-11 14:16 ` Cornelia Huck
2017-07-11 13:56 ` [Qemu-devel] [PATCH v4 07/11] pc-bios/s390-ccw: Add code for virtio feature negotiation Thomas Huth
2017-07-11 14:23 ` Cornelia Huck
2017-07-12 6:56 ` Thomas Huth
2017-07-11 13:56 ` [Qemu-devel] [PATCH v4 08/11] roms/SLOF: Update submodule to latest status Thomas Huth
2017-07-11 13:56 ` [Qemu-devel] [PATCH v4 09/11] pc-bios/s390-ccw: Add core files for the network bootloading program Thomas Huth
2017-07-11 14:30 ` Cornelia Huck
2017-07-11 13:56 ` [Qemu-devel] [PATCH v4 10/11] pc-bios/s390-ccw: Add virtio-net driver code Thomas Huth
2017-07-11 14:32 ` Cornelia Huck [this message]
2017-07-11 13:56 ` [Qemu-devel] [PATCH v4 11/11] pc-bios/s390-ccw: Link libnet into the netboot image and do the TFTP load Thomas Huth
2017-07-11 14:33 ` Cornelia Huck
2017-07-11 14:59 ` [Qemu-devel] [PATCH v4 00/11] Implement network booting in the s390-ccw BIOS no-reply
2017-07-12 8:33 ` Christian Borntraeger
2017-07-12 10:53 ` Thomas Huth
2017-07-12 11:08 ` Viktor Mihajlovski
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=20170711163228.651abd7f@dhcp-192-215.str.redhat.com \
--to=cohuck@redhat.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=alifm@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=mihajlov@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).