From: Xu Yilun <yilun.xu@linux.intel.com>
To: Philipp Stanner <pstanner@redhat.com>
Cc: Wu Hao <hao.wu@intel.com>, Tom Rix <trix@redhat.com>,
Moritz Fischer <mdf@kernel.org>, Xu Yilun <yilun.xu@intel.com>,
linux-fpga@vger.kernel.org, linux-kernel@vger.kernel.org,
Dave Airlie <airlied@redhat.com>
Subject: Re: [PATCH v2] drivers/fpga: use standard array-copy function
Date: Fri, 17 Nov 2023 16:40:33 +0800 [thread overview]
Message-ID: <ZVcnAa246LUOhlG0@yilunxu-OptiPlex-7050> (raw)
In-Reply-To: <20231114111901.19380-2-pstanner@redhat.com>
On Tue, Nov 14, 2023 at 12:19:02PM +0100, Philipp Stanner wrote:
> dfl.c utilizes memdup_user() and array_size() to copy a userspace array.
> array_size() will likely never trigger thanks to the preceeding check.
checkpatch says:
WARNING: 'preceeding' may be misspelled - perhaps 'preceding'?
#7:
array_size() will likely never trigger thanks to the preceeding check.
^^^^^^^^^^
I fixed it myself.
Acked-by: Xu Yilun <yilun.xu@intel.com>
Applied to for-next.
Thanks.
prev parent reply other threads:[~2023-11-17 8:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 11:19 [PATCH v2] drivers/fpga: use standard array-copy function Philipp Stanner
2023-11-17 8:40 ` Xu Yilun [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=ZVcnAa246LUOhlG0@yilunxu-OptiPlex-7050 \
--to=yilun.xu@linux.intel.com \
--cc=airlied@redhat.com \
--cc=hao.wu@intel.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=pstanner@redhat.com \
--cc=trix@redhat.com \
--cc=yilun.xu@intel.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 read-only IMAP folder(s) and NNTP newsgroup(s).