diff options
| author |   Jan-Simon Moeller <jsmoeller@linuxfoundation.org> | 2018-05-25 18:53:52 +0000 |
|---|---|---|
| committer |   Gerrit Code Review <gerrit@automotivelinux.org> | 2018-05-25 18:53:52 +0000 |
| commit | 88befdfd812a58fb7a36e090278ad1e70003e925 (patch) | |
| tree | dd04c9b6d8d6e534e0c2687250b18a006964bd18 /low-can-binding/diagnostic | |
| parent | 438bf4912a1174c63fac77fe72e3b320c589f431 (diff) | |
| parent | 2eb313e5330dbfa1b6eab146b3698d8ffe054347 (diff) | |
Merge "Fixing typos made in comments"flounder_5.99.1flounder/5.99.15.99.1
Diffstat (limited to 'low-can-binding/diagnostic')
| -rw-r--r-- | low-can-binding/diagnostic/diagnostic-manager.cpp | 4 | ||||
| -rw-r--r-- | low-can-binding/diagnostic/diagnostic-manager.hpp | 4 |
2 files changed, 4 insertions, 4 deletions
diff --git a/low-can-binding/diagnostic/diagnostic-manager.cpp b/low-can-binding/diagnostic/diagnostic-manager.cpp index 2f22b14d..bc335dfc 100644 --- a/low-can-binding/diagnostic/diagnostic-manager.cpp +++ b/low-can-binding/diagnostic/diagnostic-manager.cpp @@ -49,8 +49,8 @@ diagnostic_manager_t::~diagnostic_manager_t() } } -/// @brief Diagnostic manager isn't initialized at launch but after -/// CAN bus devices initialization. For the moment, it is only possible +/// @brief Diagnostic manager is not initialized at launch but after +/// the initialization of CAN bus devices. For the moment, it is only possible /// to have 1 diagnostic bus which are the first bus declared in the JSON /// description file. Configuration instance will return it. /// diff --git a/low-can-binding/diagnostic/diagnostic-manager.hpp b/low-can-binding/diagnostic/diagnostic-manager.hpp index 75d08e20..896a2b60 100644 --- a/low-can-binding/diagnostic/diagnostic-manager.hpp +++ b/low-can-binding/diagnostic/diagnostic-manager.hpp @@ -27,7 +27,7 @@ #include "../can/can-bus.hpp" #include "active-diagnostic-request.hpp" -/// Each CAN bus needs its own set of shim functions, so this should +/// Each CAN bus requires its own set of shim functions, so this should /// match the maximum CAN controller count. /// #define DIAGNOSTIC_RESPONSE_ARBITRATION_ID_OFFSET 0x8 @@ -35,7 +35,7 @@ class active_diagnostic_request_t; /// -/// @brief The core structure for running the diagnostics module by the binding. +/// @brief The core structure for running the diagnostics module of the binding. /// /// This stores details about the active requests and shims required to connect /// the diagnostics library to the CAN device. |