linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: rodrigo.alencar@analog.com, linux-kernel@vger.kernel.org,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-doc@vger.kernel.org, David Lechner <dlechner@baylibre.com>,
	Andy Shevchenko <andy@kernel.org>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Michael Hennerich <Michael.Hennerich@analog.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH 1/3] iio: frequency: adf41513: driver implementation
Date: Sun, 16 Nov 2025 16:07:02 +0000	[thread overview]
Message-ID: <20251116160702.1ac24a54@jic23-huawei> (raw)
In-Reply-To: <aRIVt5zpWmlBVjyh@smile.fi.intel.com>

On Mon, 10 Nov 2025 18:41:27 +0200
Andy Shevchenko <andriy.shevchenko@intel.com> wrote:

> On Mon, Nov 10, 2025 at 06:30:38PM +0200, Andy Shevchenko wrote:
> > On Mon, Nov 10, 2025 at 03:44:44PM +0000, Rodrigo Alencar via B4 Relay wrote:  
> 
> ...
> 
> > In any case, I stopped my review here, you have more than enough to fix.
> > Please, come next time with a tag from one whose name is in the MAINTAINERS.
> > From now on it will be my requirement as a reviewer of IIO subsystem.  
> 
> And to be more clear on this requirement (for all submissions from @analog.com
> and related): A name from approximately below list I want to see as Rb.
> 
> 	Antoniu Miclaus <antoniu.miclaus@analog.com>
> 	Marcelo Schmitt <marcelo.schmitt@analog.com>
> 	Michael Hennerich <michael.hennerich@analog.com>
>         Nuno Sá <nuno.sa@analog.com>
> 
> (those people seems experienced and I have heard of / from).
> 

From Nuno's mail seems that in general Analog actually have a better
process for this than many (which is excellent to hear btw!)
RB tags that come before being posted to the list only really have
meaning if we know and have built up trust with the reviewers.
This is different to ones on the list where we can see what the
feedback was that has been acted on.

I'll note that ADI sometimes works with external companies, so
there are various other people who would work as well. Given
that may change over time I'll not call them out explicitly but
you can probably figure out who I mean.  I have no idea if they
also help with pre submission reviews though.

Note that Andy's request here is specific to Analog given they
have the folk to do it.  I don't want this sort of requirement
to apply to folk working for other companies who have a much
smaller presence in IIO!  (just for the record, as Andy was very
clear this was a request specific to Analog).

Jonathan

p.s. Bad luck Rodrigo for being the submitter who triggered this!
Looking forward to v2 - I'll probably not add more noise by
reviewing this version.


  reply	other threads:[~2025-11-16 16:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-10 15:44 [PATCH 0/3] ADF41513/ADF41510 PLL frequency synthesizers Rodrigo Alencar via B4 Relay
2025-11-10 15:44 ` [PATCH 1/3] iio: frequency: adf41513: driver implementation Rodrigo Alencar via B4 Relay
2025-11-10 16:30   ` Andy Shevchenko
2025-11-10 16:41     ` Andy Shevchenko
2025-11-16 16:07       ` Jonathan Cameron [this message]
2025-11-11  8:43     ` Nuno Sá
2025-11-13 13:13   ` Marcelo Schmitt
2025-11-13 14:39     ` Nuno Sá
2025-11-10 15:44 ` [PATCH 2/3] dt-bindings: iio: frequency: add adf41513 Rodrigo Alencar via B4 Relay
2025-11-11  8:05   ` Krzysztof Kozlowski
2025-11-13 13:21   ` Marcelo Schmitt
2025-11-10 15:44 ` [PATCH 3/3] docs: iio: add documentation for adf41513 driver Rodrigo Alencar via B4 Relay
2025-11-10 16:38 ` [PATCH 0/3] ADF41513/ADF41510 PLL frequency synthesizers Andy Shevchenko
2025-11-16 16:10 ` Jonathan Cameron
2025-11-17  8:37   ` Nuno Sá

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20251116160702.1ac24a54@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=krzk+dt@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=rodrigo.alencar@analog.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).