From: Wang Zihan <jiyu03@qq.com>
To: joshua.crofts1@gmail.com
Cc: jic23@kernel.org, linux-iio@vger.kernel.org,
linux-doc@vger.kernel.org, Wang Zihan <jiyu03@qq.com>
Subject: Re: [PATCH v2] iio: adxl313: fix typos in documentation
Date: Sat, 2 May 2026 20:53:43 +0800 [thread overview]
Message-ID: <tencent_5E6677A3FFCB969503EE5250592E75128807@qq.com> (raw)
Hi Joshua,
Thank you for the review!
I apologize for the quick v2. The v1 had an incorrect subject format
([PATCH 1/4] instead of [PATCH]) which could cause confusion. I sent
v2 to correct this formatting issue.
I will keep the 24-hour rule in mind for future submissions.
Best regards,
Wang Zihan
next reply other threads:[~2026-05-02 12:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-02 12:53 Wang Zihan [this message]
2026-05-04 16:38 ` [PATCH v2] iio: adxl313: fix typos in documentation Jonathan Cameron
-- strict thread matches above, loose matches on Subject: below --
2026-05-02 6:07 Wang Zihan
2026-05-02 12:45 ` Joshua Crofts
2026-05-04 16:43 ` Jonathan Cameron
2026-05-04 17:21 ` Joshua Crofts
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=tencent_5E6677A3FFCB969503EE5250592E75128807@qq.com \
--to=jiyu03@qq.com \
--cc=jic23@kernel.org \
--cc=joshua.crofts1@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@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