Re: [RFC] Maintainer entry profile/contributor guide for IIO

[Joshua Crofts <joshua.crofts1@gmail.com>]

On Mon, 21 Sep 2026 10:28:24 +0100
Nuno Sá <nuno.sa@analog.com> wrote:
> > I'd propose 2 documents:
> > - entry profile - documenting the review cycle, patchwork, point people over to
> >   Sashiko, relevant git tree etc.
> > - code style - the TODO is fine for existing problems in the subsystem but doesn't
> >   point out idioms we have in IIO, i.e. not using (the awful) kernel.h, preferring
> >   devm_* functions, not failing on a mismatched ID to ensure fallback etc. This is
> >   stuff that appears a lot in patches.  
> 
> Personally I do think we have some things (not just coding style)  that are very
> specific to IIO. But maybe another docs file is not the question. Or at least one
> for humans to read :)?! Have you evaluate just having an IIO entry for
> sashiko? That way, hopefully the bot would take care about the subsystem
> specifics and preferences.
> 
> I wanted to do this myself at some point but I'm always pulled for
> something else so if this is feels like something you agree and would
> like to get done, please go ahead :)
> 
> [1]: https://github.com/masoncl/review-prompts/tree/main/kernel/subsystem
> 
> My 2 cents!
> - Nuno Sá

There was a thread about adding Sashiko reviews to IIO but it died out :(
I proposed adding an IIO-specific prompt. Any ideas on what it should contain?

As Krzysztof says, there isn't really a point in making a new doc as people
just don't read docs (I know I didn't when I was starting out, but perhaps
just consulting with an LLM was a mistake :) )

-- 
Kind regards,
Joshua Crofts