It's a trade off for which there are no firm rules.On Tue, 19 Oct 2021 10:59:49 +0300Sorry, this is my first patch, I was not aware of that.
Andriy Tryshnivskyy <andriy.tryshnivskyy@xxxxxxxxxxxxxxx> wrote:
Add IIO_CHAN_INFO_RAW to the mask and implement correspondingChange log needs to be below the --- otherwise we'll store it forever
reading "raw" attribute in scmi_iio_read_raw.
Introduce new type IIO_VAL_INT_64 to read 64-bit value
for "raw" attribute.
in git. A linked tag (which will be generated when I apply)
is sufficient for this sort of historical info.
Thanks for the explanation.
Quick question: since next version will include 2 patches,
I guess a change log should be moved back to the cover letter, right?
Sometimes changes are well isolated in individual patches, in which case
the best bet is to put the change logs in each patch, sometimes they are
more global things that affect the whole series in which case the change
log is best in the cover letter.
However, for a given series pick one or other style (don't mix!) as
otherwise it would get really confusing. Mostly no one really minds
where the log is as long as we can find it easily.
Jonathan