From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Joshua Crofts <joshua.crofts1@gmail.com>
Cc: Dan Carpenter <error27@gmail.com>,
lars@metafoo.de, Michael.Hennerich@analog.com, jic23@kernel.org,
gregkh@linuxfoundation.org, dlechner@baylibre.com,
nuno.sa@analog.com, andy@kernel.org, linux-iio@vger.kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH v2 2/2] iio: frequency: ad9832: simplify bitwise math
Date: Tue, 14 Apr 2026 10:48:20 +0300 [thread overview]
Message-ID: <ad3xRJg7LFL0Luil@ashevche-desk.local> (raw)
In-Reply-To: <CALoEA-y4Uf+LbM8w+bMA7DdW0Pcpv7AVcbdOD9GknVu5R7TKUw@mail.gmail.com>
On Tue, Apr 14, 2026 at 09:39:04AM +0200, Joshua Crofts wrote:
> On Tue, 14 Apr 2026 at 09:27, Andy Shevchenko
> <andriy.shevchenko@intel.com> wrote:
> > Yes, please slow down as you also missed a tag.
>
> Yes, I've realized that it was stupid not to wait. What is the proper
> etiquette here if the
> v3 patch doesn't have the reviewed-by tag? Should I do a RESEND PATCH or a v4?
> I've attached the tag in a reply to the v3 cover letter but not sure
> if that will do something.
In this case it was fine what you have done with attaching the missed tag,
but be careful in the future.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-04-14 7:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-11 8:58 [RESEND PATCH v2 0/2] iio: frequency: ad9832: cleanups Joshua Crofts
2026-04-11 8:58 ` [RESEND PATCH v2 1/2] iio: frequency: ad9832: remove kernel.h proxy header Joshua Crofts
2026-04-11 8:58 ` [RESEND PATCH v2 2/2] iio: frequency: ad9832: simplify bitwise math Joshua Crofts
2026-04-11 10:38 ` Dan Carpenter
2026-04-11 10:47 ` Joshua Crofts
2026-04-11 10:52 ` Dan Carpenter
2026-04-11 18:38 ` David Lechner
2026-04-14 7:27 ` Andy Shevchenko
2026-04-14 7:39 ` Joshua Crofts
2026-04-14 7:48 ` Andy Shevchenko [this message]
2026-04-14 7:26 ` [RESEND PATCH v2 0/2] iio: frequency: ad9832: cleanups Andy Shevchenko
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=ad3xRJg7LFL0Luil@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=error27@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=joshua.crofts1@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=nuno.sa@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