From: Sam Winchenbach <sam.winchenbach@framepointer.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: linux-kernel@vger.kernel.org, lars@metafoo.de,
Michael.Hennerich@analog.com, antoniu.miclaus@analog.com,
jic23@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, bpellegrino@arka.org,
Sam Winchenbach <swinchenbach@arka.org>
Subject: Re: [PATCH v7 1/6] dt-bindings: iio: filter: Add lpf/hpf freq margins
Date: Mon, 17 Mar 2025 11:07:32 -0400 [thread overview]
Message-ID: <Z9g6tPqhAoTckFBh@65YTFL3.secure.tethers.com> (raw)
In-Reply-To: <20250316-sexy-tested-cheetah-c4a2f8@krzk-bin>
On Sun, Mar 16, 2025 at 05:38:42PM +0100, Krzysztof Kozlowski wrote:
> On Sun, Mar 16, 2025 at 09:50:03AM -0400, Sam Winchenbach wrote:
> > From: Sam Winchenbach <swinchenbach@arka.org>
> >
> > Adds two properties to add a margin when automatically finding the
> > corner frequencies.
> >
> > Signed-off-by: Sam Winchenbach <swinchenbach@arka.org>
> > ---
> > .../bindings/iio/filter/adi,admv8818.yaml | 20 +++++++++++++++++++
> > 1 file changed, 20 insertions(+)
>
> I don't understand. You got my tag. No changelog here, no cover letter,
> nothing explains what happened here and why the tag is being removed.
>
Apologies,
I am still quite new to this workflow, and it deviates significantly
from my day-to-day work. I mentioned in the previous patch set that I
would like to update my email address and change:
"driver core: -> iio: core:"
I wasn't aware more than that was needed. Sorry for any confusion
this may have caused.
In the future what is the preferred way to handle a
situation like this? I wasn't aware of the cover letter feature but
that looks like a promising option.
It looks like another option is to add commentary to each patch.
I am less certain about your tag being removed - I don't fully
understand that. Is there a way to preserve that if changes are made
after you sign-off?
Sorry again about the confusion this caused,
-Sam
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2025-03-17 15:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-16 13:50 [PATCH v7 1/6] dt-bindings: iio: filter: Add lpf/hpf freq margins Sam Winchenbach
2025-03-16 13:50 ` [PATCH v7 2/6] iio: filter: admv8818: fix band 4, state 15 Sam Winchenbach
2025-03-16 13:50 ` [PATCH v7 3/6] iio: filter: admv8818: fix integer overflow Sam Winchenbach
2025-03-16 13:50 ` [PATCH v7 4/6] iio: filter: admv8818: fix range calculation Sam Winchenbach
2025-03-16 13:50 ` [PATCH v7 5/6] iio: core: Add support for writing 64 bit attrs Sam Winchenbach
2025-03-16 13:50 ` [PATCH v7 6/6] iio: filter: admv8818: Support frequencies >= 2^32 Sam Winchenbach
2025-03-16 16:38 ` [PATCH v7 1/6] dt-bindings: iio: filter: Add lpf/hpf freq margins Krzysztof Kozlowski
2025-03-17 15:07 ` Sam Winchenbach [this message]
2025-03-17 18:55 ` Jonathan Cameron
2025-03-18 15:00 ` Sam Winchenbach
2025-03-30 15:13 ` Jonathan Cameron
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=Z9g6tPqhAoTckFBh@65YTFL3.secure.tethers.com \
--to=sam.winchenbach@framepointer.org \
--cc=Michael.Hennerich@analog.com \
--cc=antoniu.miclaus@analog.com \
--cc=bpellegrino@arka.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=swinchenbach@arka.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.