[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1495710253.5393.24.camel@synopsys.com>
Date: Thu, 25 May 2017 11:04:13 +0000
From: Alexey Brodkin <Alexey.Brodkin@...opsys.com>
To: "noamca@...lanox.com" <noamca@...lanox.com>,
"linux-snps-arc@...ts.infradead.org"
<linux-snps-arc@...ts.infradead.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"liavr@...lanox.com" <liavr@...lanox.com>
Subject: Re: [PATCH 03/10] ARC: typo fix in mm/fault.c
Hi Noam,
On Thu, 2017-05-25 at 05:34 +0300, Noam Camus wrote:
> From: Liav Rehana <liavr@...lanox.com>
>
> Signed-off-by: Liav Rehana <liavr@...lanox.com>
> Signed-off-by: Noam Camus <noamca@...lanox.com>
> ---
> arch/arc/mm/fault.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arc/mm/fault.c b/arch/arc/mm/fault.c
> index 162c975..a0b7bd6 100644
> --- a/arch/arc/mm/fault.c
> +++ b/arch/arc/mm/fault.c
> @@ -207,7 +207,7 @@ void do_page_fault(unsigned long address, struct pt_regs *regs)
> /* Are we prepared to handle this kernel fault?
> *
> * (The kernel has valid exception-points in the source
> - * when it acesses user-memory. When it fails in one
> + * when it accesses user-memory. When it fails in one
> * of those points, we find it in a table and do a jump
> * to some fixup code that loads an appropriate error
> * code)
Reviewed-by: Alexey Brodkin <abrodkin@...opsys.com>
Powered by blists - more mailing lists