From: ShiHao <i.shihao.999@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: andy@kernel.org, dlechner@baylibre.com,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
mazziesaccount@gmail.com, nuno.sa@analog.com,
andriy.shevchenko@intel.com, i.shihao.999@gmail.com
Subject: Re: [PATCH v5 00/14] iio: fix spelling mistakes in comments
Date: Thu, 26 Mar 2026 17:13:27 +0530 [thread overview]
Message-ID: <acUb33haPmRWnz1g@fedora> (raw)
In-Reply-To: <20260321193217.3fa11fdc@jic23-huawei>
On Sat, Mar 21, 2026 at 07:32:17PM +0000, Jonathan Cameron wrote:
> Oddly of this whole set only patch 10 applied with out having to fall back
> to the slightly fuzzier logic patch uses compared to git am
>
> I'm not sure what caused it but Shi Hao, see if you can save
> these patches an apply them with git am. Then figure out why not?
> If that works try b4 am to pull them down and figure out what is going
> wrong.
>
> Applying by hand takes a while as I've not scripted it, so I'm keen
> whatever went wrong here doesn't reoccur!
>
> The resulting patches look fine to me on my tree.
Hello Jonathan,
Well sorry for the inconvenience, I checked them and the problem is
coming because i ran scripts/cleanfile and scripts/cleanpatch on
generated patches which is causing the error "corrupt patch at line n"
when using git am, otherwise git am is working fine with no errors.
Thanks for pointing it out i will make sure to be aware of this from
now on. Also please let me know if i need to send another version.
Best regards,
Shihao
prev parent reply other threads:[~2026-03-26 11:43 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 9:00 [PATCH v5 00/14] iio: fix spelling mistakes in comments Shi Hao
2026-03-16 9:00 ` [PATCH v5 01/14] iio: accel: fix typo celcius to Celsius Shi Hao
2026-03-21 19:11 ` Jonathan Cameron
2026-03-16 9:00 ` [PATCH v5 02/14] iio: light: fix several incorrect spellings Shi Hao
2026-03-21 19:12 ` Jonathan Cameron
2026-03-16 9:00 ` [PATCH v5 03/14] iio: adc: add an article and use digitize instead of digitalize Shi Hao
2026-03-21 19:13 ` Jonathan Cameron
2026-03-16 9:00 ` [PATCH v5 04/14] iio: imu: fix typo from adjustement to adjustment Shi Hao
2026-03-21 19:16 ` Jonathan Cameron
2026-03-16 9:00 ` [PATCH v5 05/14] iio: magnetometer: fix various spelling mistakes Shi Hao
2026-03-21 19:16 ` Jonathan Cameron
2026-03-16 9:00 ` [PATCH v5 06/14] iio: pressure: fix spelling mistakes in comments Shi Hao
2026-03-17 6:31 ` Matti Vaittinen
2026-03-21 19:17 ` Jonathan Cameron
2026-03-16 9:00 ` [PATCH v5 07/14] iio: proximity: fix typo from currenly to currently Shi Hao
2026-03-21 19:19 ` Jonathan Cameron
2026-03-16 9:00 ` [PATCH v5 08/14] iio: resolver: fix typo from degredation to degradation Shi Hao
2026-03-16 16:20 ` Andy Shevchenko
2026-03-16 16:22 ` Andy Shevchenko
2026-03-18 13:45 ` ShiHao
2026-03-18 14:49 ` Andy Shevchenko
2026-03-21 11:55 ` ShiHao
2026-03-21 16:32 ` David Lechner
2026-03-21 19:22 ` Jonathan Cameron
2026-03-16 9:00 ` [PATCH v5 09/14] iio: temp: fix spelling mistakes in comments Shi Hao
2026-03-21 19:23 ` Jonathan Cameron
2026-03-16 9:00 ` [PATCH v5 10/14] iio: test: fix typo from neeeds to needs in comment Shi Hao
2026-03-17 6:32 ` Matti Vaittinen
2026-03-21 19:24 ` Jonathan Cameron
2026-03-16 9:00 ` [PATCH v5 11/14] iio: common: fix spelling mistakes in comments Shi Hao
2026-03-21 19:25 ` Jonathan Cameron
2026-03-16 9:00 ` [PATCH v5 12/14] iio: chemical: rephrase comment and fix a typo Shi Hao
2026-03-21 19:29 ` Jonathan Cameron
2026-03-16 9:00 ` [PATCH v5 13/14] iio: cdc: fix spelling mistakes in comments Shi Hao
2026-03-16 9:00 ` [PATCH v5 14/14] iio: amplifiers: fix typo from Curren to Current Shi Hao
2026-03-16 15:00 ` [PATCH v5 00/14] iio: fix spelling mistakes in comments Andy Shevchenko
2026-03-21 19:32 ` Jonathan Cameron
2026-03-26 11:43 ` ShiHao [this message]
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=acUb33haPmRWnz1g@fedora \
--to=i.shihao.999@gmail.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mazziesaccount@gmail.com \
--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