From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: "K. Y. Srinivasan" <kys@microsoft.com>
Cc: linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
Haiyang Zhang <haiyangz@microsoft.com>
Subject: Re: [PATCH v2 0/2] Drivers: hv: vmbus: make bus ids in sysfs persistent
Date: Fri, 16 Sep 2016 13:22:58 +0200 [thread overview]
Message-ID: <87r38kxf59.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <1471989092-4190-1-git-send-email-vkuznets@redhat.com> (Vitaly Kuznetsov's message of "Tue, 23 Aug 2016 23:51:30 +0200")
Vitaly Kuznetsov <vkuznets@redhat.com> writes:
> Bus ids for VMBus devices in /sys/bus/vmbus/devices/ are not guaranteed
> to be persistent across reboot or kernel restart and this causes problems
> for some tools. E.g. kexec tools use these ids to identify NIC on kdump.
> Fix the issue by using if_instance from channel offer as the unique id
> instead of an auto incremented counter.
>
> Changes since v1:
> - Use if_instance instead of relid [K. Y. Srinivasan]
>
> Vitaly Kuznetsov (2):
> Drivers: hv: make VMBus bus ids persistent
> Drivers: hv: get rid of id in struct vmbus_channel
>
K. Y.,
I don't see these patches in your submissions to Greg. Could you please
pick them up (in case there are no issues with them in your opinion, of
course).
Thanks!
> drivers/hv/channel_mgmt.c | 2 --
> drivers/hv/vmbus_drv.c | 4 ++--
> include/linux/hyperv.h | 3 ---
> 3 files changed, 2 insertions(+), 7 deletions(-)
--
Vitaly
next prev parent reply other threads:[~2016-09-16 11:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 21:51 [PATCH v2 0/2] Drivers: hv: vmbus: make bus ids in sysfs persistent Vitaly Kuznetsov
2016-08-23 21:51 ` [PATCH v2 1/2] Drivers: hv: make VMBus bus ids persistent Vitaly Kuznetsov
2016-08-23 21:51 ` [PATCH v2 2/2] Drivers: hv: get rid of id in struct vmbus_channel Vitaly Kuznetsov
2016-09-16 11:22 ` Vitaly Kuznetsov [this message]
2016-09-16 14:11 ` [PATCH v2 0/2] Drivers: hv: vmbus: make bus ids in sysfs persistent KY Srinivasan
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=87r38kxf59.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 \
/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