diff options
| author | Lubomir Rintel <lkundrak@v3.sk> | 2017-08-23 14:05:19 +0200 |
|---|---|---|
| committer | Lubomir Rintel <lkundrak@v3.sk> | 2017-08-23 16:19:32 +0200 |
| commit | 9481bda93958565082efc87fccab5946f83efbc9 (patch) | |
| tree | a5f4845624a4082e6595c9ef3ae64d7cb361e733 | |
| parent | 9b28c9ba91f6714561db843d51557a91494fb790 (diff) | |
| download | NetworkManager-9481bda93958565082efc87fccab5946f83efbc9.tar.gz | |
clients: don't default Bluetooth to the PANU profile
No reason to, the other types are no less likely. Quite the contrary, if
the user specifies a GSM APN we're sure to use a DUN profile.
$ ./clients/cli/nmcli c add type bluetooth ifname '*' bluetooth.bdaddr 1C:E2:CC:56:6C:45 apn internet
$ nmcli c show bluetooth-1 |grep bluetooth.type
bluetooth.type: panu
^^^^ not cool
| -rw-r--r-- | clients/common/nm-meta-setting-desc.c | 11 |
1 files changed, 0 insertions, 11 deletions
diff --git a/clients/common/nm-meta-setting-desc.c b/clients/common/nm-meta-setting-desc.c index f577ebdc3b..54fe3b0c16 100644 --- a/clients/common/nm-meta-setting-desc.c +++ b/clients/common/nm-meta-setting-desc.c @@ -6614,16 +6614,6 @@ _setting_init_fcn_adsl (ARGS_SETTING_INIT_FCN) } static void -_setting_init_fcn_bluetooth (ARGS_SETTING_INIT_FCN) -{ - if (init_type == NM_META_ACCESSOR_SETTING_INIT_TYPE_CLI) { - g_object_set (NM_SETTING_BLUETOOTH (setting), - NM_SETTING_BLUETOOTH_TYPE, NM_SETTING_BLUETOOTH_TYPE_PANU, - NULL); - } -} - -static void _setting_init_fcn_cdma (ARGS_SETTING_INIT_FCN) { if (init_type == NM_META_ACCESSOR_SETTING_INIT_TYPE_CLI) { @@ -6808,7 +6798,6 @@ const NMMetaSettingInfoEditor nm_meta_setting_infos_editor[] = { NM_META_SETTING_VALID_PART_ITEM (GSM, FALSE), NM_META_SETTING_VALID_PART_ITEM (CDMA, FALSE), ), - .setting_init_fcn = _setting_init_fcn_bluetooth, ), SETTING_INFO (BOND, .valid_parts = NM_META_SETTING_VALID_PARTS ( |