From: Sasha Levin <sashal@kernel.org>
To: Adrian Vladu <avladu@cloudbasesolutions.com>
Cc: Dexuan Cui <decui@microsoft.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
KY Srinivasan <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>,
Alessandro Pilotti <apilotti@cloudbasesolutions.com>
Subject: Re: [PATCH v2] hv: tools: fixed Python pep8/flake8 warnings for lsvmbus
Date: Tue, 30 Jul 2019 18:25:00 -0400 [thread overview]
Message-ID: <20190730222500.GG29162@sasha-vm> (raw)
In-Reply-To: <F5008595B06C564AB347C30B4FDE4BC559697F85@CBSEX1.cloudbase.local>
On Tue, Jul 30, 2019 at 02:53:35PM +0000, Adrian Vladu wrote:
>Hello,
>
>There were two patches you have queued for hyperv-fixes a while ago, but I don't see them anymore in the hyperv-fixes tree:
>https://lore.kernel.org/patchwork/patch/1070848/
>https://lore.kernel.org/patchwork/patch/1070806/
>
>I have checked them and they can still be applied successfully on the latest master tree.
>Please let me know if I need to make some amends to get them merged.
They must have got lost when we dealt with the clocksource mess. I'll
re-queue these, thanks!
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-07-30 22:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 17:27 [PATCH] hv: tools: fixed Python pep8/flake8 warnings for lsvmbus Adrian Vladu
2019-05-06 17:33 ` [PATCH v2] " Adrian Vladu
2019-05-07 5:02 ` Dexuan Cui
2019-05-09 1:09 ` Sasha Levin
2019-07-30 14:53 ` Adrian Vladu
2019-07-30 22:25 ` Sasha Levin [this message]
2019-07-31 8:51 ` Adrian Vladu
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=20190730222500.GG29162@sasha-vm \
--to=sashal@kernel.org \
--cc=apilotti@cloudbasesolutions.com \
--cc=avladu@cloudbasesolutions.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.