From: 007 <zxl434815272@gmail.com>
To: Maxwell Doose <m32285159@gmail.com>
Cc: linux-gpio@vger.kernel.org, brgl@kernel.org,
warthog618@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] tools: gpio: fix ioctl name in error message
Date: Thu, 7 May 2026 08:03:39 +0800 [thread overview]
Message-ID: <04281d11-18ee-47d7-b698-1d802716049d@gmail.com> (raw)
In-Reply-To: <CAKqfh0GznF_QDr4S0KKk3c6HVfFhgEQQPO2_W6T=eTYVXnJe9Q@mail.gmail.com>
Hi, bro, I will redo it, thanks for the reminder.
Best regards
Zhang Xiaolei
On 5/5/26 01:47, Maxwell Doose wrote:
> Hi Zhang,
>
> On Mon, May 4, 2026 at 2:56 AM Zhang Xiaolei <zxl434815272@gmail.com> wrote:
>> Use the correct ioctl name in the error message.
>>
>> Signed-off-by: Zhang Xiaolei <zxl434815272@gmail.com>
>> ---
>> tools/gpio/gpio-utils.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
> [snip]
>
> Patch looks technically good but when I meant split these patches I
> meant into entirely separate patches. Please split this away from the
> patch series.
>
> best regards,
> max
next prev parent reply other threads:[~2026-05-07 0:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-03 19:00 [PATCH] tools: gpio: fix buffer overflow and add bounds check Zhang Xiaolei
2026-05-03 20:56 ` Maxwell Doose
2026-05-04 5:46 ` 007
2026-05-04 5:55 ` 007
2026-05-04 7:50 ` [PATCH v2 1/3] tools: gpio: use strscpy() for consumer name Zhang Xiaolei
2026-05-04 7:50 ` [PATCH v2 2/3] tools: gpio: validate arguments in gpiotools_request_line Zhang Xiaolei
2026-05-04 16:13 ` Maxwell Doose
2026-05-07 0:04 ` 007
2026-05-04 7:50 ` [PATCH v2 3/3] tools: gpio: fix ioctl name in error message Zhang Xiaolei
2026-05-04 17:47 ` Maxwell Doose
2026-05-07 0:03 ` 007 [this message]
2026-05-07 0:41 ` [PATCH v3] " Zhang Xiaolei
2026-05-04 12:45 ` [PATCH v2 1/3] tools: gpio: use strscpy() for consumer name David Laight
2026-05-07 0:02 ` 007
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=04281d11-18ee-47d7-b698-1d802716049d@gmail.com \
--to=zxl434815272@gmail.com \
--cc=brgl@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m32285159@gmail.com \
--cc=warthog618@gmail.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