All of lore.kernel.org
 help / color / mirror / Atom feed
From: Colin Ian King <colin.i.king@gmail.com>
To: Simon Horman <simon.horman@corigine.com>,
	Jakub Kicinski <kuba@kernel.org>,
	"David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	Huanhuan Wang <huanhuan.wang@corigine.com>,
	Steffen Klassert <steffen.klassert@secunet.com>,
	Louis Peens <louis.peens@corigine.com>,
	oss-drivers@corigine.com, netdev@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH][next] xfrm: Fix spelling mistake "tyoe" -> "type"
Date: Wed,  7 Dec 2022 09:19:19 +0000	[thread overview]
Message-ID: <20221207091919.2278416-1-colin.i.king@gmail.com> (raw)

There is a spelling mistake in a nn_err message. Fix it.

Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
---
 drivers/net/ethernet/netronome/nfp/crypto/ipsec.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/ethernet/netronome/nfp/crypto/ipsec.c b/drivers/net/ethernet/netronome/nfp/crypto/ipsec.c
index 4632268695cb..266368386836 100644
--- a/drivers/net/ethernet/netronome/nfp/crypto/ipsec.c
[next]+++ b/drivers/net/ethernet/netronome/nfp/crypto/ipsec.c
@@ -303,7 +303,7 @@ static int nfp_net_xfrm_add_state(struct xfrm_state *x)
 	}
 
 	if (x->xso.type != XFRM_DEV_OFFLOAD_CRYPTO) {
-		nn_err(nn, "Unsupported xfrm offload tyoe\n");
+		nn_err(nn, "Unsupported xfrm offload type\n");
 		return -EINVAL;
 	}
 
-- 
2.38.1


             reply	other threads:[~2022-12-07  9:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-07  9:19 Colin Ian King [this message]
2022-12-07 10:37 ` [PATCH][next] xfrm: Fix spelling mistake "tyoe" -> "type" Leon Romanovsky
2022-12-07 11:51 ` Simon Horman
2022-12-09  8:13 ` Steffen Klassert

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=20221207091919.2278416-1-colin.i.king@gmail.com \
    --to=colin.i.king@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=huanhuan.wang@corigine.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=louis.peens@corigine.com \
    --cc=netdev@vger.kernel.org \
    --cc=oss-drivers@corigine.com \
    --cc=pabeni@redhat.com \
    --cc=simon.horman@corigine.com \
    --cc=steffen.klassert@secunet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.