I am just sending a revised version with incorporations of your >> suggestions. I will create a fresh version 2 patch after everyone has >> reviewed. >> > > If you send revised version, then please send them as a separate patch > with a new version. You can mention in the commit message what you changed > in a particular version of the patch. For example: > > https://lists.gnu.org/archive/html/qemu-devel/2018-05/msg06269.html > > There should be a section which tells me which tools I have to install. > > The new files need a proper copyright message mentioning the copyright > owner. >
Okay I will make these changes. In contrast to the other documents the stuff in user uses subdirectories > and separate files at a low section level. Is this practical? > I didn't quite understand this. Also what are you thoughts on my idea of accomplishing function tracing using CTF? Do you think its a viable approach? This is written in the function tracing use case below: +Requirements +------------ + +The current tracing framework provides this functionality with :ref:`tracebuffering`. The output is +provided in the form of printing on console or saving the buffer in the form of a bin file. In order to +develop this use case using CTF we need to be able to convert either the bin file or console output to CTF. +The saved bin file must also first be transported to the host from the target for this purpose. On the other +hand console output could be written to a text file which can then be converted to CTF.
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
