Re: [PATCH v2 2/3] iio: industrialio-backend: support backend capabilities
From: Andy Shevchenko
Date: Wed Jan 14 2026 - 02:52:30 EST
On Wed, Jan 14, 2026 at 9:39 AM Tomas Melin <tomas.melin@xxxxxxxxxxx> wrote:
> On 13/01/2026 23:06, Andy Shevchenko wrote:
> > On Tue, Jan 13, 2026 at 12:12:48PM +0000, Tomas Melin wrote:
...
> >> struct iio_backend {
> >
> >> u8 idx;
> >> + u32 caps;
> >
> > Please, run `pahole` to see if there is a better place for a new member.
> > (I bet there is.)
> Indeed, there seems to be. Thanks for the suggestion, will update.
Basically it should be your, as a developer, tool at hand to check the
data type layouts whenever the new member is added or rearrangement is
made.
> >> };
...
> >> +enum iio_backend_capabilities {
> >> + IIO_BACKEND_CAP_TEST_PATTERNS = BIT(0),
> >> + IIO_BACKEND_CAP_BUFFERING = BIT(1),
> >> + IIO_BACKEND_CAP_CALIBRATION = BIT(2)
> >
> > Add trailing comma, it will allow to avoid unneeded churn in the future.
> Sounds good, was just following existing style.
I haven't checked the rest, but the rule of thumb is that:
1) potential of the adding new entries after the last one — (almost)
always add a trailing comma;
2) termination entry — never add a trailing comma;
3) exceptions are some arrays which are located on one line, like
static int foo[] = { 1, 2, 3 };
means no trailing comma.
> >> +};
--
With Best Regards,
Andy Shevchenko