From: Lakhvich Dmitriy <Ldmitriy@ru.ibm.com>
To: linux-s390@vger.kernel.org
Subject: [PATCH] qeth: autodetect layer2/3 of z/VM VSWITCH
Date: Wed, 22 Jun 2016 16:07:26 +0000 [thread overview]
Message-ID: <1466611647-4065-1-git-send-email-Ldmitriy@ru.ibm.com> (raw)
From: Lakhvich Dmitriy <LDmitriy@ru.ibm.com>
Current version of qeth driver has a problem with
layer setting for virtual z/VM nics(VSWITCH or GUEST LAN).
Such nics are supports just one layer. Setting unsupported layer produce
errors so linux user must know which layer the virtual nic supports.
This patch fix the problem, now qeth driver can detect z/VM nic's
supported layer, also to avoid errors layer changing for
z/VM virtual nics now is forbidden.
Lakhvich Dmitriy (1):
qeth: autodetect layer2/3 of z/VM VSWITCH/GUESTLAN
drivers/s390/net/qeth_core_main.c | 104 +++++++++++++++++++++++++++++++++++---
drivers/s390/net/qeth_core_sys.c | 6 +++
2 files changed, 102 insertions(+), 8 deletions(-)
--
2.5.0
reply other threads:[~2016-06-22 16:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1466611647-4065-1-git-send-email-Ldmitriy@ru.ibm.com \
--to=ldmitriy@ru.ibm.com \
--cc=linux-s390@vger.kernel.org \
/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).