From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: "K. Y. Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>,
devel@linuxdriverproject.org (open list:Hyper-V CORE AND DRIVERS),
linux-kernel@vger.kernel.org (open list)
Subject: Re: [PATCH v2] tools: hv: update lsvmbus to be compatible with python3
Date: Wed, 23 May 2018 11:29:56 +0200 [thread overview]
Message-ID: <871se2en3f.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <20180522075417.13691-1-olaf@aepfle.de> (Olaf Hering's message of "Tue, 22 May 2018 09:54:16 +0200")
Olaf Hering <olaf@aepfle.de> writes:
> Python3 changed the way how 'print' works.
> Adjust the code to a syntax that is understood by python2 and python3.
>
> Signed-off-by: Olaf Hering <olaf@aepfle.de>
What are the odds that we decide to send the same patch on the same day?
:-)
http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2018-May/121144.html
--
Vitaly
prev parent reply other threads:[~2018-05-23 9:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 7:54 Olaf Hering
2018-05-23 9:29 ` Vitaly Kuznetsov [this message]
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=871se2en3f.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=sthemmin@microsoft.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
Powered by JetHome