public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wanlong Gao <wanlong.gao@gmail.com>
To: Connor Hansen <cmdkhh@gmail.com>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation:fix the wrong file position in sched-arch.txt
Date: Mon, 13 Jun 2011 13:48:27 +0800	[thread overview]
Message-ID: <1307944107.2703.3.camel@Tux> (raw)
In-Reply-To: <BANLkTik2tgB98qyfdJJLi7_J-9_BJUp+gg@mail.gmail.com>

On 日, 2011-06-12 at 22:41 -0700, Connor Hansen wrote:
> On Sun, Jun 12, 2011 at 10:05 PM, Wanlong Gao <wanlong.gao@gmail.com> wrote:
> > On 日, 2011-06-12 at 21:56 -0700, Connor Hansen wrote:
> >> On Sun, Jun 12, 2011 at 9:35 PM, Wanlong Gao <wanlong.gao@gmail.com> wrote:
> >> > The arch i386 had changed to x86.
> >>
> >> $ grep -R "i386" Documentation/ | wc -l
> >> 155
> >>
> >> Fix them all with:
> >> grep -lZR "i386" Documentation/ | xargs -0 -l sed -i -e 's/i386/x86/g'
> >>
> >> or send ~ 100 patches
> > You see, but not all i386 can change to x86 in Documentation/
> > right?
> 
> Documentation/filesystems/fuse.txt:  limited anyway to 32 pages (which
> is 128kbyte on i386).
<snip>
> I don't see any problems,
> Connor
Hmm...I'm not sure, but I had send another patch which changed all
arch/i386 to arch/x86, I think it all be OK.

Thanks
Best regards

> 
> >
> > Thanks
> >>
> >> -Connor



      reply	other threads:[~2011-06-13  7:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-13  4:35 [PATCH] Documentation:fix the wrong file position in sched-arch.txt Wanlong Gao
2011-06-13  4:56 ` Connor Hansen
2011-06-13  5:05   ` Wanlong Gao
2011-06-13  5:41     ` Connor Hansen
2011-06-13  5:48       ` Wanlong Gao [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=1307944107.2703.3.camel@Tux \
    --to=wanlong.gao@gmail.com \
    --cc=cmdkhh@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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