summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAndre Hartmann <aha_1980@gmx.de>2019-07-27 21:45:31 +0200
committerAndre Hartmann <aha_1980@gmx.de>2019-07-29 11:55:28 +0200
commit0ea12029c3d8883ba928d33e36a397657e6b1ae5 (patch)
treefefa614eb431a20ee26309b5d0ecd59cecfa228e
parent9f5b8ba590d424f82498fca5f2cc8594b1757ff0 (diff)
QCanBusDevice: Rewrap documentation
Change-Id: I615a9113db1fcc2f787950dac70847d852d06a1d Reviewed-by: Alex Blasche <alexander.blasche@qt.io> Reviewed-by: Denis Shienkov <denis.shienkov@gmail.com>
-rw-r--r--src/serialbus/qcanbusdevice.cpp7
1 files changed, 4 insertions, 3 deletions
diff --git a/src/serialbus/qcanbusdevice.cpp b/src/serialbus/qcanbusdevice.cpp
index af004d4..713dc52 100644
--- a/src/serialbus/qcanbusdevice.cpp
+++ b/src/serialbus/qcanbusdevice.cpp
@@ -790,9 +790,10 @@ QVector<QCanBusFrame> QCanBusDevice::readAllFrames()
As per CAN bus specification, frames of type
\l {QCanBusFrame::RemoteRequestFrame} {remote transfer request (RTR)}
- do not have a payload, but a length from 0 to 8 (including). This length indicates
- the expected response payload length from the remote party. Therefore when sending a RTR frame using
- this function it may still be required to set an arbitrary payload on \a frame. The length of
+ do not have a payload, but a length from 0 to 8 (including). This length
+ indicates the expected response payload length from the remote party.
+ Therefore when sending a RTR frame using this function it may still
+ be required to set an arbitrary payload on \a frame. The length of
the arbitrary payload is what is set as size expectation for the RTR frame.
\sa QCanBusFrame::setPayload()