Fri, Nov 08, 2019 at 04:08:22PM CET, parav@xxxxxxxxxxxx wrote: > > >> -----Original Message----- >> From: Jiri Pirko <jiri@xxxxxxxxxxx> >> Sent: Friday, November 8, 2019 4:45 AM >> To: Parav Pandit <parav@xxxxxxxxxxxx> >> Cc: alex.williamson@xxxxxxxxxx; davem@xxxxxxxxxxxxx; >> kvm@xxxxxxxxxxxxxxx; netdev@xxxxxxxxxxxxxxx; Saeed Mahameed >> <saeedm@xxxxxxxxxxxx>; kwankhede@xxxxxxxxxx; leon@xxxxxxxxxx; >> cohuck@xxxxxxxxxx; Jiri Pirko <jiri@xxxxxxxxxxxx>; linux- >> rdma@xxxxxxxxxxxxxxx >> Subject: Re: [PATCH net-next 19/19] mtty: Optionally support mtty alias >> >> Thu, Nov 07, 2019 at 05:08:34PM CET, parav@xxxxxxxxxxxx wrote: >> >Provide a module parameter to set alias length to optionally generate >> >mdev alias. >> > >> >Example to request mdev alias. >> >$ modprobe mtty alias_length=12 >> > >> >Make use of mtty_alias() API when alias_length module parameter is set. >> > >> >Signed-off-by: Parav Pandit <parav@xxxxxxxxxxxx> >> >> This patch looks kind of unrelated to the rest of the set. >> I think that you can either: >> 1) send this patch as a separate follow-up to this patchset >> 2) use this patch as a user and push out the mdev alias patches out of this >> patchset to a separate one (I fear that this was discussed and declined >> before). >Yes, we already discussed to run mdev 5-6 patches as pre-patch before this series when reviewed on kvm mailing list. >Alex was suggesting to package with this series as mlx5_core being the first user. >Series will have conflict (not this patch) if Jason Wang's series [9] is merged first. >So please let me know how shall we do it. Just remove this patch from the set and push it later on individually (if ever). > >[9] https://patchwork.ozlabs.org/patch/1190425 > >
