From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 966BA280A56 for ; Thu, 18 Jun 2026 13:22:21 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781788942; cv=none; b=lRtMAqumPAFXKWwpbmGZcsId2ie+8Ub9GmScYx/XXfMgqgB9Bzbo1Solj35kHResqkBOsZb+eUa5U0jjXeKL5MIkrxoEb8gBD1+U/JMhTI5khhUMA1m0J4fISyn3Ysp7z1ZgZiqlRQxptlA0VqNqN0mCtlJaZqYEm5yVh7IteGY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781788942; c=relaxed/simple; bh=BXR+B0SvxcgDPXvP2gM0Ba0NVZrxbaXZEgFLFsvoyC8=; h=From:Subject:To:Cc:In-Reply-To:References:Content-Type:Date: Message-Id; b=bHu4xlJVVhJtn2azGISuCUsPzrTcDtk9s9gtdG8m6daEeZuQJU/F/p0xbUKkOTPzXfD71OdMtQbg/fLOJrCU+/uSh/5HJCtdrizG1Xkci/7kI82X8V0hEwJSnPRadeHwOkwiLPmr+vxnsRRqby2az/EU6O5Q1U3vSvqQVEwdkDk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=hGMWibO/; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="hGMWibO/" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 150FA1F000E9; Thu, 18 Jun 2026 13:22:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1781788941; bh=BXR+B0SvxcgDPXvP2gM0Ba0NVZrxbaXZEgFLFsvoyC8=; h=From:Subject:Reply-To:To:Cc:In-Reply-To:References:Date; b=hGMWibO/x2QwqrH+9Gihpx5UEAlJgpb0VbhU6B4etg+yk41ZQL2uhYpZXzBGyBxsN rlALj/cBaAa6/n1mXSoLpwCsqM6/9XHa4obfB28Oko7B/YtaCj7gJT9Y6AG4duN/SW 3GTZyvMDKWkH9Gmrdlsfp8yagZpy1/wKrIRk7Qr5SmuDSDGZuIitaOYfSGtjENtkCr 3+aVQMKhij/QZDnGk7EMFYqIxdkHANg2fttW6E0XKiChkGr0rhxC5inCSYeLcyi0bF HFK/eJwNez2Vi8XzAX2SNdF+DQqbylFCl/v2QfOixiQ3M7fKet9kK7RHmRlqVTy8CP n5QaEs1nypC0Q== From: sashiko-bot@kernel.org Subject: Re: [PATCH v3 2/2] scsi: leapraid: Add driver documentation Reply-To: sashiko-reviews@lists.linux.dev To: "Dongdong Hao" Cc: linux-scsi@vger.kernel.org In-Reply-To: References: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Date: Thu, 18 Jun 2026 13:22:20 +0000 Message-Id: <20260618132221.150FA1F000E9@smtp.kernel.org> Precedence: bulk X-Mailing-List: linux-scsi@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Thank you for your contribution! Sashiko AI review found 1 potential issue(= s) to consider: - [Medium] The documentation incorrectly names the module parameter for mul= tipath support as `enable_mpio` instead of `enable_mp`. -- commit 958c37a9e9c4054d4110e1b080f8c3be25877cb6 Author: Dongdong Hao scsi: leapraid: Add driver documentation This patch adds the necessary documentation for the LeapRAID SCSI driver to the kernel's documentation tree. > diff --git a/Documentation/scsi/leapraid.rst b/Documentation/scsi/leaprai= d.rst > new file mode 100644 > index 0000000000000..e4a6a61c13f8e > --- /dev/null > +++ b/Documentation/scsi/leapraid.rst [ ... ] > +2. enable_mpio > +-------------- > + > +This parameter enables or disables multipath support for target devices. [Severity: Medium] Should this module parameter be documented as enable_mp instead of enable_mpio? If users attempt to configure multipath support using enable_mpio via the kernel command line or modprobe config, they will encounter unknown parameter errors. > +When set to 1, multipath functionality is enabled (default), allowing > +multiple paths to be established. Setting it to 0 disables multipath > +handling. > + > +3. msix_disable --=20 Sashiko AI review =C2=B7 https://sashiko.dev/#/patchset/cover.1781767278.gi= t.doubled@leap-io-kernel.com?part=3D2