From: Jithu Joseph <jithu.joseph@intel.com>
To: ilpo.jarvinen@linux.intel.com, hdegoede@redhat.com, markgross@kernel.org
Cc: linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org, jithu.joseph@intel.com,
ashok.raj@intel.com, tony.luck@intel.com, rostedt@goodmis.org,
sathyanarayanan.kuppuswamy@intel.com, ravi.v.shankar@intel.com,
patches@lists.linux.dev
Subject: [PATCH 0/3] Miscelleanous In Field Scan changes
Date: Fri, 12 Apr 2024 10:23:46 -0700 [thread overview]
Message-ID: <20240412172349.544064-1-jithu.joseph@intel.com> (raw)
Hi Hans/Ilpo,
Bunch of In Field Scan patches
Patch1 - Classify Scan controller malfunction as untested
Patch2 - Trace output format related
Patch3 - Disable irq during a particular load step
Jithu Joseph (3):
platform/x86/intel/ifs: Classify error scenarios correctly
platform/x86/intel/ifs: trace: display batch num in hex
platform/x86/intel/ifs: Disable irq during one load stage
include/trace/events/intel_ifs.h | 2 +-
drivers/platform/x86/intel/ifs/load.c | 2 ++
drivers/platform/x86/intel/ifs/runtest.c | 27 +++++++++++++-----------
3 files changed, 18 insertions(+), 13 deletions(-)
base-commit: fec50db7033ea478773b159e0e2efb135270e3b7
--
2.25.1
next reply other threads:[~2024-04-12 17:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 17:23 Jithu Joseph [this message]
2024-04-12 17:23 ` [PATCH 1/3] platform/x86/intel/ifs: Classify error scenarios correctly Jithu Joseph
2024-04-12 18:32 ` Kuppuswamy Sathyanarayanan
2024-04-12 19:31 ` Joseph, Jithu
2024-04-12 20:46 ` Kuppuswamy Sathyanarayanan
2024-04-15 15:10 ` Hans de Goede
2024-04-12 17:23 ` [PATCH 2/3] platform/x86/intel/ifs: trace: display batch num in hex Jithu Joseph
2024-04-12 18:45 ` Kuppuswamy, Sathyanarayanan
2024-04-12 17:23 ` [PATCH 3/3] platform/x86/intel/ifs: Disable irq during one load stage Jithu Joseph
2024-04-12 19:13 ` Kuppuswamy Sathyanarayanan
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=20240412172349.544064-1-jithu.joseph@intel.com \
--to=jithu.joseph@intel.com \
--cc=ashok.raj@intel.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=patches@lists.linux.dev \
--cc=platform-driver-x86@vger.kernel.org \
--cc=ravi.v.shankar@intel.com \
--cc=rostedt@goodmis.org \
--cc=sathyanarayanan.kuppuswamy@intel.com \
--cc=tony.luck@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).