Hi Johan, > The NOT_PAIRED status is only really suitable for operations where being > paired is a pre-requisite. Using it e.g. for the mgmt_pair_device > command seems unintuitive. In the case that either the local or the > remote user responds with a negative PIN Code response the "PIN or Key > Missing" HCI status will be generated. This patch changes the mapping of > this status from the NOT_PAIRED mgmt status to the more intuitive > AUTH_FAILED mgmt status. > > Signed-off-by: Johan Hedberg <johan.hedberg@xxxxxxxxx> > --- > I had trouble deciding whether we should use REJECTED or AUTH_FAILED > here, but eventually went with AUTH_FAILED. If someone thinks REJECTED > is better and has convincing reasons for it I can change it. > > net/bluetooth/mgmt.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) patch has been applied to bluetooth-next tree. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
