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

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

On Sat, 19 Sep 2026 20:53:36 +0200
Krzysztof Kozlowski <krzk@kernel.org> wrote:
> >> Maintainers file already defines git tree. Patchwork as well. Please
> >> read existing docs first, because it seems you propose to duplicate it
> >> (including submitting patches and other process documents).
> >>
> >> Subsystem profiles are expected to document things which are done here a
> >> bit differently or specific subsystem expectations, narrowing general
> >> kernel process docs.
> >>
> >>  
> >>> - 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.    
> >>
> >> You just described standard kernel practice. Don't create documents just
> >> for sake of creating them.  
> > 
> > I'd like you to point me to a doc that says that fallbacks are a thing
> > and you shouldn't do dev_err_probe() on a bad ID (to name one "quirk").
> > 
> > Otherwise I agree that some of it is repetitive.  
> 
> You wrote devm and kernel.h...

I was referring to the next paragraph. Yeah, perhaps it's not the greatest
idea to add new docs if people don't read them. Someone should instead come
up with a way to *force* newcomers to read documentation instead.

-- 
Kind regards,
Joshua Crofts