Miri Korenblit <miriam.rachel.korenblit@xxxxxxxxx> writes: > From: Ilan Peer <ilan.peer@xxxxxxxxx> > > In some cases, when an interface is added by user space, user space > might not know yet what is the intended type of the interface, e.g., > before a P2P Group Ownership Negotiation (GON) an interface is added > but only at the end of the GON flow the final interface type is > determined. This doesn't allow the kernel drivers to prepare for the > actual interface type, e.g., make resources available for the > interface type etc. > > Generally, adding an interface doesn't necessarily imply that it will > actually be used soon, and as described the interface might not be used > with the type it's added as. > > This new API allows user space to indicate that it does indeed intend to > use the interface soon, along with the types (of which the interface > must be one) that may be selected for that usage. This will allow the > underlying driver to adjust resources accordingly. > > Signed-off-by: Ilan Peer <ilan.peer@xxxxxxxxx> > Reviewed-by: Johannes Berg <johannes.berg@xxxxxxxxx> > Tested-by: iil_jenkins iil_jenkins <EC.GER.UNIX.IIL.JENKINS@xxxxxxxxx> This new command just looks weird to me, do we really need it? I would expect to see a workaround like this in out-of-tree drivers but not in upstream. -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
