From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760615AbdEYLEU (ORCPT ); Thu, 25 May 2017 07:04:20 -0400 Received: from smtprelay4.synopsys.com ([198.182.47.9]:53914 "EHLO smtprelay.synopsys.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751297AbdEYLER (ORCPT ); Thu, 25 May 2017 07:04:17 -0400 From: Alexey Brodkin To: "noamca@mellanox.com" , "linux-snps-arc@lists.infradead.org" CC: "linux-kernel@vger.kernel.org" , "liavr@mellanox.com" Subject: Re: [PATCH 03/10] ARC: typo fix in mm/fault.c Thread-Topic: [PATCH 03/10] ARC: typo fix in mm/fault.c Thread-Index: AQHS1P+NGLe9N1s3OUqM0TouYtdkvaIEwcKA Date: Thu, 25 May 2017 11:04:13 +0000 Message-ID: <1495710253.5393.24.camel@synopsys.com> References: <1495679660-9598-1-git-send-email-noamca@mellanox.com> <1495679660-9598-4-git-send-email-noamca@mellanox.com> In-Reply-To: <1495679660-9598-4-git-send-email-noamca@mellanox.com> Accept-Language: en-US, ru-RU Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.121.8.122] Content-Type: text/plain; charset="utf-8" Content-ID: <2D3AD1619606C0468DF0B8DC968C74BA@internal.synopsys.com> MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id v4PB6VLr018039 Hi Noam, On Thu, 2017-05-25 at 05:34 +0300, Noam Camus wrote: > From: Liav Rehana > > Signed-off-by: Liav Rehana > Signed-off-by: Noam Camus > --- >  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