Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Cc: herbert@gondor.apana.org.au, davem@davemloft.net,
	gustavoars@kernel.org, qat-linux@intel.com,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
	rdunlap@infradead.org
Subject: Re: [PATCH] drivers: crypto: qat: qat_common: Inside the comment a spelling fixed in adf_pf2vf_msg.c
Date: Tue, 9 Feb 2021 10:22:35 +0000	[thread overview]
Message-ID: <20210209102223.GA118045@silpixa00400314> (raw)
In-Reply-To: <20210203145506.11928-1-unixbhaskar@gmail.com>

Thanks.

I'm going to consolidate this with the previous patch, improve the
commit message and resubmit.

Regards,

-- 
Giovanni

On Wed, Feb 03, 2021 at 08:25:06PM +0530, Bhaskar Chowdhury wrote:
> 
> s/messge/message/
> 
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
> ---
>  drivers/crypto/qat/qat_common/adf_pf2vf_msg.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/crypto/qat/qat_common/adf_pf2vf_msg.c b/drivers/crypto/qat/qat_common/adf_pf2vf_msg.c
> index 8b090b7ae8c6..a1b77bd7a894 100644
> --- a/drivers/crypto/qat/qat_common/adf_pf2vf_msg.c
> +++ b/drivers/crypto/qat/qat_common/adf_pf2vf_msg.c
> @@ -169,7 +169,7 @@ static int __adf_iov_putmsg(struct adf_accel_dev *accel_dev, u32 msg, u8 vf_nr)
>   * @msg:	Message to send
>   * @vf_nr:	VF number to which the message will be sent
>   *
> - * Function sends a messge from the PF to a VF
> + * Function sends a message from the PF to a VF
>   *
>   * Return: 0 on success, error code otherwise.
>   */
> --
> 2.26.2
> 

      reply	other threads:[~2021-02-09 10:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-03 14:55 [PATCH] drivers: crypto: qat: qat_common: Inside the comment a spelling fixed in adf_pf2vf_msg.c Bhaskar Chowdhury
2021-02-09 10:22 ` Giovanni Cabiddu [this message]

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=20210209102223.GA118045@silpixa00400314 \
    --to=giovanni.cabiddu@intel.com \
    --cc=davem@davemloft.net \
    --cc=gustavoars@kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=qat-linux@intel.com \
    --cc=rdunlap@infradead.org \
    --cc=unixbhaskar@gmail.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