From 9240e8d65978b3e43ba51627d82f318d6f026669 Mon Sep 17 00:00:00 2001 From: Paul Jones Date: Fri, 20 Aug 2021 13:48:08 +1000 Subject: [PATCH 1/2] Update README.md Fix typo in example --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 1a3b9c23..2025ba6f 100644 --- a/README.md +++ b/README.md @@ -722,7 +722,7 @@ public: // or the high-power mode above 17 dBm. In other words, it lets the // LMIC-determined policy determine what's to be done. - virutal TxPowerPolicy_t getTxPowerPolicy( + virtual TxPowerPolicy_t getTxPowerPolicy( TxPowerPolicy_t policy, int8_t requestedPower, uint32_t frequency From fda13b3c2ea4f6e7252f46c8648056b42742aa4b Mon Sep 17 00:00:00 2001 From: Paul Jones Date: Fri, 20 Aug 2021 13:52:49 +1000 Subject: [PATCH 2/2] Update README.md --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 2025ba6f..b0929a73 100644 --- a/README.md +++ b/README.md @@ -712,7 +712,7 @@ In some boards require much more advanced management. The LMIC has a very flexib The full example looks like this: ```c++ -class cMyHlaConfiguration_t : public Arduino_LMIC::HalConfiguration_t +class cMyHalConfiguration_t : public Arduino_LMIC::HalConfiguration_t { public: // ... @@ -730,7 +730,7 @@ public: { return policy; } - } + }; ``` #### HalConfiguration_t methods