Documentation: rtla: Correct command line example

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2189439

commit 877d95d
Author:    Pierre Gondois <pierre.gondois@arm.com>
Date:      Thu Oct 6 10:44:09 2022 +0200

	Documentation: rtla: Correct command line example

	The '-t/-T' parameters seem to have been swapped:
	-t/--trace[=file]: save the stopped trace
	to [file|timerlat_trace.txt]
	-T/--thread us: stop trace if the thread latency
	is higher than the argument in us

	Swap them back.

Signed-off-by: Pierre Gondois <pierre.gondois@arm.com>
Acked-by: Daniel Bristot de Oliveira <bristot@kernel.org>
Link: https://lore.kernel.org/r/20221006084409.3882542-1-pierre.gondois@arm.com
Signed-off-by: Jonathan Corbet <corbet@lwn.net>

Signed-off-by: John Kacur <jkacur@redhat.com>

Author: John Kacur

Documentation/tools/rtla/rtla-timerlat-top.rst

@@ -39,7 +39,7 @@ higher than *30 us*. It is also set to stop the session if a *Thread* timer
 latency higher than *30 us* is hit. Finally, it is set to save the trace
 buffer if the stop condition is hit::
 
-  [root@alien ~]# rtla timerlat top -s 30 -t 30 -T
+  [root@alien ~]# rtla timerlat top -s 30 -T 30 -t
                    Timer Latency
     0 00:00:59   |          IRQ Timer Latency (us)        |         Thread Timer Latency (us)
   CPU COUNT      |      cur       min       avg       max |      cur       min       avg       max