Linux IIO development
 help / color / mirror / Atom feed
From: Sam Winchenbach <sam.winchenbach@framepointer.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
	antoniu.miclaus@analog.com, lars@metafoo.de,
	Michael.Hennerich@analog.com
Subject: Re: [PATCH v2] iio: filter: admv8818: fix range calculation
Date: Wed, 5 Mar 2025 08:11:17 -0500	[thread overview]
Message-ID: <Z8hNdR21h7b7V8Kx@65YTFL3.secure.tethers.com> (raw)
In-Reply-To: <20250304233411.3fac7c69@jic23-huawei>

On Tue, Mar 04, 2025 at 11:34:11PM +0000, Jonathan Cameron wrote:
> On Thu, 20 Feb 2025 08:17:11 -0500
> Sam Winchenbach <sam.winchenbach@framepointer.org> wrote:
> 
> > Corrects the upper range of LPF Band 4 from 18.5 GHz to 18.85 GHz per
> > the ADMV8818 datasheet
> > 
> Hi Sam,
> 
> Just a trivial process thing.  If you are sending updated code
> and there isn't an obvious reason why when someone looks at the
> old patch set (e.g. no reviews asking for changes etc) please
> reply to that.
> 
> At times where reviewers (such as me on this occasion) are running
> way behind they might look at wrong version otherwise.
> 
> Jonathan

Hi Jonathan,

Just to clarify, if I update the patches in, for example v2, then I should
reply to the v2 email with the new patch set?

That makes sense... it looks like I can use: "--in-reply-to=<Message-id>" with
git send-email.

Sorry for any confusion this may have caused.

Thanks,
-Sam

  reply	other threads:[~2025-03-05 13:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-20 13:17 [PATCH v2] iio: filter: admv8818: fix range calculation Sam Winchenbach
2025-03-04 23:34 ` Jonathan Cameron
2025-03-05 13:11   ` Sam Winchenbach [this message]
2025-03-05 14:23     ` 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=Z8hNdR21h7b7V8Kx@65YTFL3.secure.tethers.com \
    --to=sam.winchenbach@framepointer.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=antoniu.miclaus@analog.com \
    --cc=jic23@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