From: Greg KH <gregkh@linuxfoundation.org>
To: Tony Luck <tony.luck@intel.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
"Joseph, Jithu" <jithu.joseph@intel.com>,
markgross@kernel.org, ashok.raj@intel.com,
ravi.v.shankar@intel.com, linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org, patches@lists.linux.dev
Subject: Re: [PATCH 1/2] Documentation: Correct IFS reload documentation
Date: Sun, 10 Jul 2022 22:00:49 +0200 [thread overview]
Message-ID: <Yssv8a2/wzLlAQQn@kroah.com> (raw)
In-Reply-To: <20220710182521.60642-2-tony.luck@intel.com>
On Sun, Jul 10, 2022 at 11:25:20AM -0700, Tony Luck wrote:
> From: Jithu Joseph <jithu.joseph@intel.com>
>
> The location where the scan image is stored is incorrect
> in the current documentation. Fix this.
>
> Fixes: 34604d289167("Documentation: In-Field Scan")
Our tools will complain about this line, please use the correct format
so you don't get grumpy emails from the linux-next maintainer.
thanks,
greg k-h
next prev parent reply other threads:[~2022-07-10 20:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 15:19 [PATCH] platform/x86/intel/ifs: Allow non-default names for IFS image Jithu Joseph
2022-07-08 15:28 ` Greg KH
2022-07-08 18:34 ` Joseph, Jithu
2022-07-10 10:15 ` Greg KH
2022-07-10 13:42 ` Hans de Goede
2022-07-10 13:53 ` Greg KH
2022-07-10 14:08 ` Hans de Goede
2022-07-10 16:04 ` Joseph, Jithu
2022-07-10 16:09 ` Hans de Goede
2022-07-10 18:25 ` [PATCH 0/2] Two fixes for IFS Tony Luck
2022-07-10 18:25 ` [PATCH 1/2] Documentation: Correct IFS reload documentation Tony Luck
2022-07-10 20:00 ` Greg KH [this message]
2022-07-10 18:25 ` [PATCH 2/2] platform/x86/intel/ifs: return error on load failure Tony Luck
2022-07-10 19:57 ` [PATCH 0/2] Two fixes for IFS Hans de Goede
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=Yssv8a2/wzLlAQQn@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ashok.raj@intel.com \
--cc=hdegoede@redhat.com \
--cc=jithu.joseph@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=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