From: Julia Lawall <julia.lawall@inria.fr>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
kernel-janitors@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 12/30] drivers: net: packetengines: fix typos in comments
Date: Mon, 14 Mar 2022 18:13:10 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2203141812231.2561@hadrien> (raw)
In-Reply-To: <20220314100630.0ee93704@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
On Mon, 14 Mar 2022, Jakub Kicinski wrote:
> On Mon, 14 Mar 2022 12:53:36 +0100 Julia Lawall wrote:
> > Various spelling mistakes in comments.
> > Detected with the help of Coccinelle.
>
> FWIW it would be easier to process the patches if they were posted
> individually, there are no dependencies here.
OK, I hesitated between different options. If I send more, I will do as
you suggest.
thanks,
julia
next prev parent reply other threads:[~2022-03-14 17:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 11:53 [PATCH 00/30] fix typos in comments Julia Lawall
2022-03-14 11:53 ` [PATCH 03/30] ath6kl: " Julia Lawall
2022-03-18 15:39 ` Kalle Valo
2022-03-14 11:53 ` [PATCH 10/30] mt76: mt7915: " Julia Lawall
2022-03-14 11:53 ` [PATCH 12/30] drivers: net: packetengines: " Julia Lawall
2022-03-14 17:06 ` Jakub Kicinski
2022-03-14 17:13 ` Julia Lawall [this message]
2022-03-14 11:53 ` [PATCH 19/30] rtlwifi: rtl8821ae: " Julia Lawall
2022-03-15 0:29 ` Pkshih
2022-03-16 15:31 ` Kalle Valo
2022-03-14 11:53 ` [PATCH 20/30] airo: " Julia Lawall
2022-03-14 11:53 ` [PATCH 27/30] can: ucan: " Julia Lawall
2022-03-14 12:05 ` Marc Kleine-Budde
2022-03-14 13:03 ` Julia Lawall
2022-03-14 13:36 ` Marc Kleine-Budde
2022-03-14 20:30 ` [PATCH 00/30] " patchwork-bot+netdevbpf
2022-03-15 4:33 ` Martin K. Petersen
2022-03-15 13:40 ` (subset) " Mark Brown
2022-03-19 3:56 ` 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=alpine.DEB.2.22.394.2203141812231.2561@hadrien \
--to=julia.lawall@inria.fr \
--cc=davem@davemloft.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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