From: patchwork-bot+netdevbpf@kernel.org
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, corbet@lwn.net,
linux-doc@vger.kernel.org, tj@kernel.org,
lizefan.x@bytedance.com, hannes@cmpxchg.org,
cgroups@vger.kernel.org, agk@redhat.com, snitzer@kernel.org,
dm-devel@redhat.com, mchehab@kernel.org,
linux-media@vger.kernel.org, linux-mm@kvack.org,
dan.j.williams@intel.com, vishal.l.verma@intel.com,
dave.jiang@intel.com, nvdimm@lists.linux.dev, vkoul@kernel.org,
dmaengine@vger.kernel.org, song@kernel.org,
linux-raid@vger.kernel.org, gregkh@linuxfoundation.org,
linux-usb@vger.kernel.org, jdelvare@suse.com, linux@roeck-us.net,
linux-hwmon@vger.kernel.org, jiri@nvidia.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org, paulmck@kernel.org,
frederic@kernel.org, quic_neeraju@quicinc.com,
josh@joshtriplett.org, rcu@vger.kernel.org, jejb@linux.ibm.com,
martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
sparclinux@vger.kernel.org
Subject: Re: [PATCH 0/9] Documentation: correct lots of spelling errors (series 2)
Date: Tue, 31 Jan 2023 12:10:17 +0000 [thread overview]
Message-ID: <167516701747.19012.10728935395396675001.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230129231053.20863-1-rdunlap@infradead.org>
Hello:
This patch was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Sun, 29 Jan 2023 15:10:44 -0800 you wrote:
> Maintainers of specific kernel subsystems are only Cc-ed on their
> respective patches, not the entire series. [if all goes well]
>
> These patches are based on linux-next-20230127.
>
>
> [PATCH 1/9] Documentation: admin-guide: correct spelling
> [PATCH 2/9] Documentation: driver-api: correct spelling
> [PATCH 3/9] Documentation: hwmon: correct spelling
> [PATCH 4/9] Documentation: networking: correct spelling
> [PATCH 5/9] Documentation: RCU: correct spelling
> [PATCH 6/9] Documentation: scsi/ChangeLog*: correct spelling
> [PATCH 7/9] Documentation: scsi: correct spelling
> [PATCH 8/9] Documentation: sparc: correct spelling
> [PATCH 9/9] Documentation: userspace-api: correct spelling
>
> [...]
Here is the summary with links:
- [4/9] Documentation: networking: correct spelling
https://git.kernel.org/netdev/net-next/c/a266ef69b890
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-01-31 12:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 23:10 [PATCH 0/9] Documentation: correct lots of spelling errors (series 2) Randy Dunlap
2023-01-29 23:10 ` [PATCH 3/9] Documentation: hwmon: correct spelling Randy Dunlap
2023-01-30 0:39 ` Guenter Roeck
2023-01-31 12:10 ` patchwork-bot+netdevbpf [this message]
2023-01-31 12:17 ` [PATCH 0/9] Documentation: correct lots of spelling errors (series 2) Paolo Abeni
2023-02-02 18:09 ` Jonathan Corbet
2023-02-02 18:33 ` Randy Dunlap
2023-02-02 18:39 ` [dm-devel] " Bart Van Assche
2023-02-02 18:46 ` Jonathan Corbet
2023-02-02 18:54 ` James Bottomley
2023-02-14 16:57 ` (subset) " Martin K. Petersen
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=167516701747.19012.10728935395396675001.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=agk@redhat.com \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=davem@davemloft.net \
--cc=dm-devel@redhat.com \
--cc=dmaengine@vger.kernel.org \
--cc=edumazet@google.com \
--cc=frederic@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@cmpxchg.org \
--cc=jdelvare@suse.com \
--cc=jejb@linux.ibm.com \
--cc=jiri@nvidia.com \
--cc=josh@joshtriplett.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lizefan.x@bytedance.com \
--cc=martin.petersen@oracle.com \
--cc=mchehab@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=paulmck@kernel.org \
--cc=quic_neeraju@quicinc.com \
--cc=rcu@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=snitzer@kernel.org \
--cc=song@kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=tj@kernel.org \
--cc=vishal.l.verma@intel.com \
--cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).