From: "Gary Chu(楚光庆)" <chuguangqing@inspur.com>
To: Alex Williamson <alex@shazbot.org>
Cc: ast <ast@kernel.org>, daniel <daniel@iogearbox.net>,
andrii <andrii@kernel.org>, martin.lau <martin.lau@linux.dev>,
eddyz87 <eddyz87@gmail.com>, song <song@kernel.org>,
yonghong.song <yonghong.song@linux.dev>,
john.fastabend <john.fastabend@gmail.com>,
kpsingh <kpsingh@kernel.org>, sdf <sdf@fomichev.me>,
haoluo <haoluo@google.com>, jolsa <jolsa@kernel.org>,
kwankhede <kwankhede@nvidia.com>, bpf <bpf@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
kvm <kvm@vger.kernel.org>
Subject: Re: Re: [PATCH v2 1/1] samples/bpf: Fix spelling typo in samples/bpf
Date: Wed, 15 Oct 2025 08:59:33 +0800 [thread overview]
Message-ID: <68eef1b8.1.4heY4R8JIaj5heY4@inspur.com> (raw)
In-Reply-To: <20251014140035.31bd9154@shazbot.org>
[-- Attachment #1: Type: text/plain, Size: 240 bytes --]
>I'd suggest this go through bpf since it touches more there. For mtty,
>
>Acked-by: Alex Williamson <alex@shazbot.org>
Can I understand this as splitting into two separate threads: one for BPF and one for mtty?
Best regards
Chu Guangqing
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2683 bytes --]
next prev parent reply other threads:[~2025-10-15 0:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 6:08 [PATCH v2 0/1] Some spelling error fixes in samples directory Chu Guangqing
2025-10-14 6:08 ` [PATCH v2 1/1] samples/bpf: Fix spelling typo in samples/bpf Chu Guangqing
2025-10-14 6:48 ` Menglong Dong
2025-10-14 7:54 ` Chu Guangqing
2025-10-14 20:00 ` Alex Williamson
2025-10-15 0:59 ` Gary Chu(楚光庆) [this message]
2025-10-15 1:05 ` Alex Williamson
2025-10-14 7:53 Chu Guangqing
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=68eef1b8.1.4heY4R8JIaj5heY4@inspur.com \
--to=chuguangqing@inspur.com \
--cc=alex@shazbot.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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
all inboxes | Powered by JetHome®