From: Jonathan Corbet <corbet@lwn.net>
To: Alex Hung <alex.hung@canonical.com>
Cc: tglx@linutronix.de, mchehab+samsung@kernel.org,
akpm@linux-foundation.org, pawan.kumar.gupta@linux.intel.com,
jgross@suse.com, linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation: fix a typo for intel_iommu=nobounce
Date: Tue, 25 Feb 2020 03:34:39 -0700 [thread overview]
Message-ID: <20200225033439.77b3b73c@lwn.net> (raw)
In-Reply-To: <20200219192133.7375-1-alex.hung@canonical.com>
On Wed, 19 Feb 2020 12:21:33 -0700
Alex Hung <alex.hung@canonical.com> wrote:
> "untrusted" was mis-spelled as "unstrusted"
>
> Signed-off-by: Alex Hung <alex.hung@canonical.com>
> ---
> Documentation/admin-guide/kernel-parameters.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index dbc22d684627..c8b7ec949453 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -1775,7 +1775,7 @@
> provided by tboot because it makes the system
> vulnerable to DMA attacks.
> nobounce [Default off]
> - Disable bounce buffer for unstrusted devices such as
> + Disable bounce buffer for untrusted devices such as
> the Thunderbolt devices. This will treat the untrusted
> devices as the trusted ones, hence might expose security
> risks of DMA attacks.
Applied, thanks.
jon
prev parent reply other threads:[~2020-02-25 10:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 19:21 [PATCH] Documentation: fix a typo for intel_iommu=nobounce Alex Hung
2020-02-25 10:34 ` Jonathan Corbet [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=20200225033439.77b3b73c@lwn.net \
--to=corbet@lwn.net \
--cc=akpm@linux-foundation.org \
--cc=alex.hung@canonical.com \
--cc=jgross@suse.com \
--cc=linux-doc@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=tglx@linutronix.de \
/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 NNTP newsgroup(s).