From: ShiHao <i.shihao.999@gmail.com>
To: Dhruva Gole <d-gole@ti.com>
Cc: andriy.shevchenko@intel.com, andy@kernel.org,
dlechner@baylibre.com, jic23@kernel.org,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
m-chawdhry@ti.com, daniel.baluta@nxp.com, simona.toaca@nxp.com,
i.shihao.999@gmail.com
Subject: Re: [PATCH v4 0/6] iio: fix spelling mistakes in comments
Date: Sun, 15 Mar 2026 18:14:20 +0530 [thread overview]
Message-ID: <abappH2DGoqTU82e@fedora> (raw)
In-Reply-To: <20260311101007.gaqcner4fzamyirm@lcpd911>
On Wed, Mar 11, 2026 at 03:40:07PM +0530, Dhruva Gole wrote:
>
> I just tried applying this series locally, on top of linux-next tag: next-20260310
>
> Could you please make sure to use git format-patch with the option --base HEAD~N
> where N is the number of your patches?
> This will help identify what you used as the base commit for all your
> changes. Make sure it's usually on top of the latest linux-next.
>
> I also ran checkpatch on them, and saw a bunch of errors and warnings,
> not sure if you've run it on your end and ensured it's clean?
>
> Also, in the changelog, please add links to your previous revisions.
> This make reviewing things and getting context much easier.
> Best regards,
> Dhruva Gole
> Texas Instruments Incorporated
Hi everyone,
I have a quick question regarding my patch series. I noticed that a
similar patch was already submitted and has been accepted, so I removed
those changes from my series. However, I have added a few additional
fixes and the series has now grown to about 13 patches. The original
series had only 6 patches, so I am unsure whether I should send this
as v5 or resend it as a new series. I would appreciate any guidance.
I want to avoid creating unnecessary noise on the mailing list.
Best regards,
Shi Hao
next prev parent reply other threads:[~2026-03-15 12:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 9:39 [PATCH v4 0/6] iio: fix spelling mistakes in comments Shi Hao
2026-03-11 9:39 ` [PATCH v4 1/6] iio: accel: fix typo celcius to Celsius Shi Hao
2026-03-11 9:39 ` [PATCH v4 2/6] iio: adc: fix spelling mistakes in comments Shi Hao
2026-03-11 9:39 ` [PATCH v4 3/6] iio: amplifiers: fix typo Curren to Current Shi Hao
2026-03-11 9:39 ` [PATCH v4 4/6] iio: cdc: fix spelling mistakes in comments Shi Hao
2026-03-11 9:39 ` [PATCH v4 5/6] iio: chemical: rephrase sentence and fix typo in comment Shi Hao
2026-03-11 9:39 ` [PATCH v4 6/6] iio: common: fix spelling mistakes in comments Shi Hao
2026-03-11 10:10 ` [PATCH v4 0/6] iio: " Dhruva Gole
2026-03-15 12:44 ` ShiHao [this message]
2026-03-15 18:05 ` Jonathan Cameron
2026-03-15 13:07 ` 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=abappH2DGoqTU82e@fedora \
--to=i.shihao.999@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=d-gole@ti.com \
--cc=daniel.baluta@nxp.com \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-chawdhry@ti.com \
--cc=simona.toaca@nxp.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 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.