From: Sam Winchenbach <sam.winchenbach@framepointer.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
antoniu.miclaus@analog.com, lars@metafoo.de,
Michael.Hennerich@analog.com, jic23@kernel.org
Subject: Re: [PATCH v3 2/2] dt-bindings: iio: filter: Add lpf/hpf freq margins
Date: Tue, 25 Feb 2025 08:49:07 -0500 [thread overview]
Message-ID: <Z73KUzqe5VmITJVB@65YTFL3.secure.tethers.com> (raw)
In-Reply-To: <fe1b0dde-f899-4303-bd2a-b19098edcae8@kernel.org>
On Tue, Feb 25, 2025 at 08:42:04AM +0100, Krzysztof Kozlowski wrote:
> On 24/02/2025 18:50, Sam Winchenbach wrote:
> > Adds two properties to add a margin when automatically finding the
> > corner frequencies.
> >
> > Signed-off-by: Sam Winchenbach <sam.winchenbach@framepointer.org>
>
> <form letter>
> Please use scripts/get_maintainers.pl to get a list of necessary people
> and lists to CC. It might happen, that command when run on an older
> kernel, gives you outdated entries. Therefore please be sure you base
> your patches on recent Linux kernel.
>
> Tools like b4 or scripts/get_maintainer.pl provide you proper list of
> people, so fix your workflow. Tools might also fail if you work on some
> ancient tree (don't, instead use mainline) or work on fork of kernel
> (don't, instead use mainline). Just use b4 and everything should be
> fine, although remember about `b4 prep --auto-to-cc` if you added new
> patches to the patchset.
>
> You missed at least devicetree list (maybe more), so this won't be
> tested by automated tooling. Performing review on untested code might be
> a waste of time.
>
> Please kindly resend and include all necessary To/Cc entries.
> </form letter>
Updated the maintainers list per your instruction and resubmitted as v4.
Thank you for your assistance.
>
> > ---
> > .../devicetree/bindings/iio/filter/adi,admv8818.yaml | 12 ++++++++++++
> > 1 file changed, 12 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/iio/filter/adi,admv8818.yaml b/Documentation/devicetree/bindings/iio/filter/adi,admv8818.yaml
> > index b77e855bd594..1be6f1fe4bfc 100644
> > --- a/Documentation/devicetree/bindings/iio/filter/adi,admv8818.yaml
> > +++ b/Documentation/devicetree/bindings/iio/filter/adi,admv8818.yaml
> > @@ -44,6 +44,16 @@ properties:
> > '#clock-cells':
> > const: 0
> >
> > + adi,lpf-margin-hz:
> > + description:
> > + Sets minimum low-pass corner frequency to the frequency of rf_in plus this value when in auto mode.
>
> Wrap according to coding style.
Updated in the v4 patch.
>
>
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2025-02-25 13:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 17:50 [PATCH v3 1/2] iio: filter: admv8818: fix range calculation Sam Winchenbach
2025-02-24 17:50 ` [PATCH v3 2/2] dt-bindings: iio: filter: Add lpf/hpf freq margins Sam Winchenbach
2025-02-25 7:42 ` Krzysztof Kozlowski
2025-02-25 13:49 ` Sam Winchenbach [this message]
2025-02-24 17:59 ` [PATCH v3 1/2] iio: filter: admv8818: fix range calculation Sam Winchenbach
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=Z73KUzqe5VmITJVB@65YTFL3.secure.tethers.com \
--to=sam.winchenbach@framepointer.org \
--cc=Michael.Hennerich@analog.com \
--cc=antoniu.miclaus@analog.com \
--cc=jic23@kernel.org \
--cc=krzk@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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