From: Randy Dunlap <rdunlap@xenotime.net>
To: sedat.dilek@gmail.com
Cc: Sedat Dilek <sedat.dilek@googlemail.com>,
Joerg Roedel <joro@8bytes.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] amd_iommu: Fix typo in kernel-parameters.txt
Date: Tue, 06 Dec 2011 08:59:26 -0800 [thread overview]
Message-ID: <4EDE49EE.4060909@xenotime.net> (raw)
In-Reply-To: <CA+icZUXFT0bC8x-3E96sYya_ayiLvKMM4s7kR3J2XAh6C9tQdw@mail.gmail.com>
On 12/06/2011 06:20 AM, Sedat Dilek wrote:
> On Tue, Dec 6, 2011 at 3:17 PM, Joerg Roedel <joro@8bytes.org> wrote:
>> On Mon, Dec 05, 2011 at 11:08:32PM +0100, Sedat Dilek wrote:
>>>
>>> Signed-off-by: Sedat Dilek <sedat.dilek@gmail.com>
>>> ---
>>> Documentation/kernel-parameters.txt | 2 +-
>>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>>
>>> diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
>>> index a0c5c5f..da50377 100644
>>> --- a/Documentation/kernel-parameters.txt
>>> +++ b/Documentation/kernel-parameters.txt
>>> @@ -320,7 +320,7 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
>>> on: enable for both 32- and 64-bit processes
>>> off: disable for both 32- and 64-bit processes
>>>
>>> - amd_iommu= [HW,X86-84]
>>> + amd_iommu= [HW,X86-64]
>>> Pass parameters to the AMD IOMMU driver in the system.
>>> Possible values are:
>>> fullflush - enable flushing of IO/TLB entries when
>>
>> Applied, thanks. Please Cc me directly on future patches so it is easier
>> to notice for me :)
>
> Sorry for this, I followed stupidly get_maintainer.pl script :-).
Not a problem -- I would have applied it soon.
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2011-12-06 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 22:08 [PATCH] amd_iommu: Fix typo in kernel-parameters.txt Sedat Dilek
2011-12-06 14:17 ` Joerg Roedel
2011-12-06 14:20 ` Sedat Dilek
2011-12-06 16:59 ` Randy Dunlap [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=4EDE49EE.4060909@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=joro@8bytes.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=sedat.dilek@googlemail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.