From: Jithu Joseph <jithu.joseph@intel•com>
To: bp@alien8•de
Cc: rdunlap@infradead•org, jithu.joseph@intel•com,
linux-kernel@vger•kernel.org, linux-next@vger•kernel.org,
sfr@canb•auug.org.au, ashok.raj@intel•com, tony.luck@intel•com
Subject: [RESEND PATCH] platform/x86/intel/ifs: Add missing documentation entry
Date: Fri, 2 Dec 2022 21:24:45 -0800 [thread overview]
Message-ID: <20221203052445.502450-1-jithu.joseph@intel.com> (raw)
In-Reply-To: <774fd22a-aaee-758d-8195-77bac783ecbc@infradead.org>
Documentation for test_num member of struct ifs_data is missing [1].
Link: https://lore.kernel.org/lkml/774fd22a-aaee-758d-8195-77bac783ecbc@infradead.org/ [1]
Reported-by: Stephen Rothwell <sfr@canb•auug.org.au>
Signed-off-by: Jithu Joseph <jithu.joseph@intel•com>
---
-Resending to "bp@alien8•de" as "bp@suse•de" reported undeliverable
drivers/platform/x86/intel/ifs/ifs.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/platform/x86/intel/ifs/ifs.h b/drivers/platform/x86/intel/ifs/ifs.h
index da1474e1d8eb..046e39304fd5 100644
--- a/drivers/platform/x86/intel/ifs/ifs.h
+++ b/drivers/platform/x86/intel/ifs/ifs.h
@@ -208,6 +208,7 @@ union ifs_status {
* @status: it holds simple status pass/fail/untested
* @scan_details: opaque scan status code from h/w
* @cur_batch: number indicating the currently loaded test file
+ * @test_num: number indicating the test type
*/
struct ifs_data {
int integrity_cap_bit;
base-commit: 1a63b58082869273bfbab1b945007193f7bd3a78
--
2.25.1
next prev parent reply other threads:[~2022-12-03 5:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 4:26 linux-next: Tree for Dec 2 Stephen Rothwell
2022-12-03 3:05 ` linux-next: Tree for Dec 2 (drivers/platform/x86/intel/ifs/ifs.h) Randy Dunlap
2022-12-03 5:04 ` [PATCH] platform/x86/intel/ifs: Add missing documentation entry Jithu Joseph
2022-12-03 5:24 ` Jithu Joseph [this message]
2022-12-03 5:57 ` [RESEND PATCH] " Randy Dunlap
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=20221203052445.502450-1-jithu.joseph@intel.com \
--to=jithu.joseph@intel$(echo .)com \
--cc=ashok.raj@intel$(echo .)com \
--cc=bp@alien8$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rdunlap@infradead$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tony.luck@intel$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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