[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170212152020.6021f4e3@lwn.net>
Date: Sun, 12 Feb 2017 15:20:20 -0700
From: Jonathan Corbet <corbet@....net>
To: Nathan Howard <adanhawthorn@...il.com>
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] Documentation: DMA-ISA-LPC.txt
On Thu, 9 Feb 2017 18:36:36 -0500
Nathan Howard <adanhawthorn@...il.com> wrote:
> Fixed spelling issue.
>
> Signed-off-by: Nathan Howard <adanhawthorn@...il.com>
> ---
> Documentation/DMA-ISA-LPC.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/DMA-ISA-LPC.txt b/Documentation/DMA-ISA-LPC.txt
> index b1a1983..c413313 100644
> --- a/Documentation/DMA-ISA-LPC.txt
> +++ b/Documentation/DMA-ISA-LPC.txt
> @@ -42,7 +42,7 @@ requirements you pass the flag GFP_DMA to kmalloc.
>
> Unfortunately the memory available for ISA DMA is scarce so unless you
> allocate the memory during boot-up it's a good idea to also pass
> -__GFP_REPEAT and __GFP_NOWARN to make the allocater try a bit harder.
> +__GFP_REPEAT and __GFP_NOWARN to make the allocator try a bit harder.
>
> (This scarcity also means that you should allocate the buffer as
> early as possible and not release it until the driver is unloaded.)
Applied, thanks.
jon
Powered by blists - more mailing lists