use ubus.STATUS_NOT_FOUND if the uspot instance has not been found. A…

[pierrejoye]

Trivial litle change but handy to get the right error

Before:

ubus call 'uspotfilter' 'client_list'  "{'interface': 'captive2'}"
Command failed: Invalid argument

With STATUS_NOT_FOUND:

ubus call 'uspotfilter' 'client_list'  "{'interface': 'captive2'}"
Command failed: Not found

[f00b4r0]

Good catch, but a few formatting issues with your patch commit message: plese check the commit history and reformat accordingly (loosely based on kernel commit message styling).

Also please add a SoB line (even if I myself forgot to do so on the last commit, that was a mistake not to be repeated ;)

[pierrejoye]

Good catch, but a few formatting issues with your patch commit message: plese check the commit history and reformat accordingly (loosely based on kernel commit message styling).

Will do!

Also please add a SoB line (even if I myself forgot to do so on the last commit, that was a mistake not to be repeated ;)

Done :)

[f00b4r0]

I'm actually having second thoughts about this: I think INVALID_ARGUMENT is actually correct: while a client may be "not found", sending a wrong uspot name as parameter is invalid since uspot names are statically defined in configuration file. So I think it's better to keep things as they are so that NOT_FOUND is only used for elements that are added/removed dynamically. Otherwise there can be ambiguity between "not found" client or uspot.