Kalle Valo <kv...@codeaurora.org> writes: >> Since we've been working on this for so long and already use the term >> DQA broadly, we thought it wouldn't be necessary to explain more when >> we are finally enabling it by default. But of course I can change that >> if you prefer. > > I guessed I could find more information from the history and I know this > is obvious to your team, but it's not obvious to everyone. The commit > log should always answer the questions "Why?" and this isn't answering > that. For example, I need this information when sending pull requests to > Dave and I'm sure lots of other people find it useful as well, > especially when enabling a new feature. > > So I'm not asking for a long essay, something like this would be > adequate: > > "Run DQA flows by default, as long as the FW supports it. It's currently > supported on 1234, 3456 and 7654, maybe more in the future. DQA improves > latency when X is used or throughput when Y is disabled. On the downside > it sometimes slows down throughput when using Z but that's still > accetable as it's so rarely used."
Oh, I forgot that the acronym should be also spelled out in the commit log. -- Kalle Valo
