From: Randy Dunlap <rdunlap@infradead.org>
To: Aditya Srivastava <yashsri421@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org, herbert@gondor.apana.org.au,
corbet@lwn.net, nayna@linux.ibm.com,
linux-kernel@vger.kernel.org, pfsmorigo@gmail.com,
linux-crypto@vger.kernel.org, leitao@debian.org,
lukas.bulwahn@gmail.com,
linux-kernel-mentees@lists.linuxfoundation.org,
davem@davemloft.net, paulus@samba.org
Subject: Re: [PATCH] crypto: nx: fix incorrect kernel-doc comment syntax in files
Date: Sun, 21 Mar 2021 10:34:16 -0700 (PDT) [thread overview]
Message-ID: <84443584-2cbf-5945-2b6-b7a057a72540@infradead.org> (raw)
In-Reply-To: <20210321123007.15505-1-yashsri421@gmail.com>
Looks good. Thanks.
Acked-by: Randy Dunlap <rdunlap@infradead.org>
next prev parent reply other threads:[~2021-03-21 17:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-21 12:30 [PATCH] crypto: nx: fix incorrect kernel-doc comment syntax in files Aditya Srivastava
2021-03-21 17:34 ` Randy Dunlap [this message]
2021-03-26 9:34 ` Herbert Xu
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=84443584-2cbf-5945-2b6-b7a057a72540@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=leitao@debian.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lukas.bulwahn@gmail.com \
--cc=nayna@linux.ibm.com \
--cc=paulus@samba.org \
--cc=pfsmorigo@gmail.com \
--cc=yashsri421@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