From: Yueh-Shun Li <shamrocklee@posteo.net>
To: Jakub Kicinski <kuba@kernel.org>
Cc: jgg@ziepe.ca, leon@kernel.org, anthony.l.nguyen@intel.com,
davem@davemloft.net, kvalo@kernel.org, jejb@linux.ibm.com,
pabeni@redhat.com, apw@canonical.com, joe@perches.com,
linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
linux-wireless@vger.kernel.org, linux-scsi@vger.kernel.org,
mptcp@lists.linux.dev, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/8] Fix comment typos about "transmit"
Date: Fri, 23 Jun 2023 08:51:39 +0000 [thread overview]
Message-ID: <50a88781b9e2a80588438c315167bbec@posteo.net> (raw)
In-Reply-To: <168748862634.32034.1394302200661050543.git-patchwork-notify@kernel.org>
Dear Maintainer,
On 23.06.2023 04:50, patchwork-bot+netdevbpf@kernel.org wrote:
> Hello:
>
> This series was applied to netdev/net-next.git (main)
> by Jakub Kicinski <kuba@kernel.org>:
>
> On Thu, 22 Jun 2023 01:26:21 +0000 you wrote:
>> Fix typos about "transmit" missing the first "s"
>> found by searching with keyword "tram" in the first 7
>> patches.
>>
>> Add related patterns to "scripts/spelling.txt" in the
>> last patch.
>>
>> [...]
Thanks for merging!
> Here is the summary with links:
> - [1/8] RDMA/rxe: fix comment typo
> (no matching commit)
> - [2/8] i40e, xsk: fix comment typo
> https://git.kernel.org/netdev/net-next/c/b028813ac973
> - [3/8] zd1211rw: fix comment typo
> (no matching commit)
> - [4/8] scsi: fix comment typo
> (no matching commit)
> - [5/8] tcp: fix comment typo
> https://git.kernel.org/netdev/net-next/c/304b1875ba02
> - [6/8] net/tls: fix comment typo
> https://git.kernel.org/netdev/net-next/c/a0e128ef88e4
> - [7/8] selftests: mptcp: connect: fix comment typo
> (no matching commit)
> - [8/8] scripts/spelling.txt: Add "transmit" patterns
> (no matching commit)
>
> You are awesome, thank you!
Should I rebase the local branch onto netdev/net-next/main
and send the "no matching commit" patches again?
Best regards,
Shamrock
next prev parent reply other threads:[~2023-06-23 8:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 1:26 [PATCH 0/8] Fix comment typos about "transmit" Yueh-Shun Li
2023-06-22 1:26 ` [PATCH 1/8] RDMA/rxe: fix comment typo Yueh-Shun Li
2023-06-22 5:27 ` Zhu Yanjun
2023-06-22 1:26 ` [PATCH 2/8] i40e, xsk: " Yueh-Shun Li
2023-06-22 1:26 ` [PATCH 3/8] zd1211rw: " Yueh-Shun Li
2023-07-25 14:47 ` [3/8] wifi: zd1211rw: fix typo "tranmits" Kalle Valo
2023-06-22 1:26 ` [PATCH 4/8] scsi: fix comment typo Yueh-Shun Li
2023-06-22 1:26 ` [PATCH 5/8] tcp: " Yueh-Shun Li
2023-06-22 1:26 ` [PATCH 6/8] net/tls: " Yueh-Shun Li
2023-06-22 1:26 ` [PATCH 7/8] selftests: mptcp: connect: " Yueh-Shun Li
2023-06-22 8:19 ` Matthieu Baerts
2023-06-22 1:26 ` [PATCH 8/8] scripts/spelling.txt: Add "transmit" patterns Yueh-Shun Li
2023-06-22 2:09 ` Randy Dunlap
2023-06-23 2:50 ` [PATCH 0/8] Fix comment typos about "transmit" patchwork-bot+netdevbpf
2023-06-23 8:51 ` Yueh-Shun Li [this message]
2023-06-23 9:19 ` Matthieu Baerts
2023-06-23 10:36 ` Johannes Berg
2023-06-23 15:12 ` Jakub Kicinski
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=50a88781b9e2a80588438c315167bbec@posteo.net \
--to=shamrocklee@posteo.net \
--cc=anthony.l.nguyen@intel.com \
--cc=apw@canonical.com \
--cc=davem@davemloft.net \
--cc=jejb@linux.ibm.com \
--cc=jgg@ziepe.ca \
--cc=joe@perches.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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