RE: [PATCH 0/3] drivers/hv: make max_num_channels_supported configurable

2020-12-05 Thread Michael Kelley
From: Max Stolze Sent: Saturday, December 5, 2020 12:32 PM > > On 05/12/2020 19:27, Michael Kelley wrote: > > From: Stefan Eschenbacher > >> > >> According to the TODO comment in hyperv_vmbus.h the value in macro > >> MAX_NUM_CHANNELS_SUPPORTED should be configurable. The first patch > >>

Re: [PATCH 0/3] drivers/hv: make max_num_channels_supported configurable

2020-12-05 Thread Max Stolze
On 05/12/2020 19:27, Michael Kelley wrote: > From: Stefan Eschenbacher >> >> According to the TODO comment in hyperv_vmbus.h the value in macro >> MAX_NUM_CHANNELS_SUPPORTED should be configurable. The first patch >> accomplishes that by introducting uint max_num_channels_supported as >>

RE: [PATCH 0/3] drivers/hv: make max_num_channels_supported configurable

2020-12-05 Thread Michael Kelley
From: Stefan Eschenbacher > > According to the TODO comment in hyperv_vmbus.h the value in macro > MAX_NUM_CHANNELS_SUPPORTED should be configurable. The first patch > accomplishes that by introducting uint max_num_channels_supported as > module parameter. > Also macro

[PATCH 0/3] drivers/hv: make max_num_channels_supported configurable

2020-12-05 Thread Stefan Eschenbacher
According to the TODO comment in hyperv_vmbus.h the value in macro MAX_NUM_CHANNELS_SUPPORTED should be configurable. The first patch accomplishes that by introducting uint max_num_channels_supported as module parameter. Also macro MAX_NUM_CHANNELS_SUPPORTED_DEFAULT is introduced with value 256,