netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Colin Ian King <colin.i.king@gmail.com>
Cc: Saeed Mahameed <saeedm@nvidia.com>,
	"David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Yevgeny Kliteynik <kliteyn@nvidia.com>,
	netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
	kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net/mlx5: Fix spelling mistake "destoy" -> "destroy"
Date: Sun, 6 Nov 2022 20:12:14 +0200	[thread overview]
Message-ID: <Y2f4/ihY0cfmzSiG@unreal> (raw)
In-Reply-To: <20221031080104.773325-1-colin.i.king@gmail.com>

On Mon, Oct 31, 2022 at 08:01:04AM +0000, Colin Ian King wrote:
> There is a spelling mistake in an error message. Fix it.
> 
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> ---
>  drivers/net/ethernet/mellanox/mlx5/core/steering/dr_table.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 

Thanks,
Reviewed-by: Leon Romanovsky <leonro@nvidia.com>

BTW,
➜  kernel git:(net-next) git grep "destoy"
drivers/cpufreq/pasemi-cpufreq.c: * module init and destoy
drivers/cpufreq/ppc_cbe_cpufreq.c: * module init and destoy
drivers/hid/hid-logitech-hidpp.c:                       /* autocenter spring destoyed */
drivers/hwtracing/coresight/coresight-tmc-etr.c:         * events are simply not used an freed as events are destoyed.  We still
drivers/net/ethernet/mellanox/mlx5/core/steering/dr_table.c:            mlx5dr_err(tbl->dmn, "Failed to destoy sw owned table\n");
include/net/caif/cfpkt.h: * pkt Packet to be destoyed.
net/netfilter/nf_nat_core.c:     * Else, when the conntrack is destoyed, nf_nat_cleanup_conntrack()


  reply	other threads:[~2022-11-06 18:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31  8:01 [PATCH] net/mlx5: Fix spelling mistake "destoy" -> "destroy" Colin Ian King
2022-11-06 18:12 ` Leon Romanovsky [this message]
2022-11-11 22:49 ` Saeed Mahameed

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=Y2f4/ihY0cfmzSiG@unreal \
    --to=leon@kernel.org \
    --cc=colin.i.king@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=kliteyn@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=saeedm@nvidia.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;
as well as URLs for NNTP newsgroup(s).