From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Matt LaPlante <kernel1@cyberdogtech.com>
Cc: linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH 18-rc2] Fix typos in /Documentation : 'H'-'M'
Date: Mon, 24 Jul 2006 22:15:05 -0700 [thread overview]
Message-ID: <20060724221505.c1e927ba.rdunlap@xenotime.net> (raw)
In-Reply-To: <20060725010315.816b40e9.kernel1@cyberdogtech.com>
On Tue, 25 Jul 2006 01:03:15 -0400 Matt LaPlante wrote:
> On Mon, 24 Jul 2006 20:46:05 -0700
> "Randy.Dunlap" <rdunlap@xenotime.net> wrote:
>
> > >
> > > If your hardware supports more than one io address, and your driver can
> > > choose which one program the hardware to, starting from the more exotic
> > ^insert: to
> >
> > >
> > > -the core of the new scheduler are the following mechanizms:
> > > +The core of the new scheduler are the following mechanisms:
> >
> > s/are/contains/
> >
> > > - *two*, priority-ordered 'priority arrays' per CPU. There is an 'active'
> >
> > drop comma
> >
> > > opinion still after having already compiled the kernel.
> > > - Q: Why I cannot find the IBM MCA SCSI support in the config menue?
> > > + Q: Why I cannot find the IBM MCA SCSI support in the config menu?
> >
> > Q: Why can I not find ...?
> > or
> > Q: Why can't I find ...?
> >
> > > A: You have to activate MCA bus support, first.
> > > Q: Where can I find the latest info about this driver?
> > > A: See the file MAINTAINERS for the current WWW-address, which offers
> >
> > Rest look good to me.
> >
>
> Edited patch below.
Acked-by: Randy Dunlap <rdunlap@xenotime.net>
Thanks.
---
~Randy
prev parent reply other threads:[~2006-07-25 5:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-24 23:27 [PATCH 18-rc2] Fix typos in /Documentation : 'H'-'M' Matt LaPlante
2006-07-25 3:46 ` Randy.Dunlap
2006-07-25 5:03 ` Matt LaPlante
2006-07-25 5:15 ` Randy.Dunlap [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=20060724221505.c1e927ba.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=kernel1@cyberdogtech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).