public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Amerigo Wang <amwang@redhat.com>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	rdunlap@xenotime.net, mingo@elte.hu
Subject: Re: [Patch 2/2] Doc: move Documentation/exception.txt into x86 subdir
Date: Sun, 31 May 2009 11:31:49 +0800	[thread overview]
Message-ID: <4A21FA25.2000007@redhat.com> (raw)
In-Reply-To: <1243414594.3109.10.camel@localhost.localdomain>

Jaswinder Singh Rajput wrote:
>>> What is the reason of this name change exception.txt -> extable.txt
>>>   
>>>       
>> Hello,
>>
>> Because this doc explains how exception tables work on x86, not the 
>> hardware concept
>> "exceptions" of x86 CPU, thus extable.txt is much more reasonable. :)
>>
>>     
>
> In such case you can use exception-tables.txt or
> exception-tables-howto.txt
>   

OK, I will update my patch. :)

Thanks.


  reply	other threads:[~2009-05-31  3:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-27  7:27 [Patch 1/2] Doc: update Documentation/exception.txt Amerigo Wang
2009-05-27  7:28 ` [Patch 2/2] Doc: move Documentation/exception.txt into x86 subdir Amerigo Wang
2009-05-27  7:50   ` Amerigo Wang
2009-05-27  8:24   ` Jaswinder Singh Rajput
2009-05-27  8:37     ` Amerigo Wang
2009-05-27  8:56       ` Jaswinder Singh Rajput
2009-05-31  3:31         ` Amerigo Wang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-05-31  4:46 [Patch 1/2] Doc: update Documentation/exception.txt Amerigo Wang
2009-05-31  4:46 ` [Patch 2/2] Doc: move Documentation/exception.txt into x86 subdir Amerigo Wang
2009-07-01 20:03 [PATCH " Randy Dunlap
2009-07-06 22:15 [PATCH 2/2] doc: " Randy Dunlap
2009-07-08 22:02 [PATCH 2/2] Doc: " Randy Dunlap

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=4A21FA25.2000007@redhat.com \
    --to=amwang@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=jaswinder@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rdunlap@xenotime.net \
    /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