From: Grant Grundler <grundler@parisc-linux.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Grant Grundler <grundler@parisc-linux.org>,
Andrew Morton <akpm@osdl.org>, Greg KH <greg@kroah.com>,
Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-pci@atrey.karlin.mff.cuni.cz,
Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
Subject: Re: [PATCH] Update Documentation/pci.txt v7
Date: Mon, 25 Dec 2006 00:59:12 -0700 [thread overview]
Message-ID: <20061225075912.GA32499@colo.lackof.org> (raw)
In-Reply-To: <20061224111622.e22bfd8a.randy.dunlap@oracle.com>
On Sun, Dec 24, 2006 at 11:16:22AM -0800, Randy Dunlap wrote:
> On Sat, 23 Dec 2006 23:07:26 -0700 Grant Grundler wrote:
>
> > +10. Legacy I/O port free driver
> > +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> That subject (and patches with similar subject) confuses me.
> It's difficult to associate the adjectives correctly.
Agreed. This was the original section name and I didn't
have a better idea.
> I suppose it just needs some hyphens/dashes, like:
>
> 10. Legacy-I/O-port-free driver
>
> but that's ETOOMUCH. Maybe ?
>
> 10. Stop using legacy I/O space
Yeah, that is good too.
I changed it to "10. pci_enable_device_bars() and Legacy I/O Port space".
The goal of this section is to introduce the new PCI function
and why one should use it.
...
> > +Thus, timing sensitive code should add readl() where the CPU is
> > +expected to wait before doing other work. The classic "bit banging"
> > +sequence works fine for I/O Port space:
> > +
> > + for (i=8; --i; val >>= 1) {
>
> Please use: i = 8;
> to match CodingStyle. (and below)
Definitely....Sorry, I thought someone already asked me to change this.
I thought I did. Changed now in both cases.
> Rest looks good to me.
v8 will be posted shortly.
thanks Randy!
grant
next prev parent reply other threads:[~2006-12-25 7:59 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 8:05 [PATCH 1/5] Update Documentation/pci.txt Hidetoshi Seto
2006-11-22 8:05 ` Hidetoshi Seto
2006-11-22 8:54 ` Arjan van de Ven
2006-11-22 18:28 ` Grant Grundler
2006-11-22 18:28 ` Grant Grundler
2006-11-24 0:38 ` Hidetoshi Seto
2006-11-24 0:38 ` Hidetoshi Seto
2006-11-24 5:12 ` Grant Grundler
2006-11-24 5:12 ` Grant Grundler
2006-11-24 6:05 ` Hidetoshi Seto
2006-11-24 6:05 ` Hidetoshi Seto
2006-12-06 7:26 ` Greg KH
2006-12-07 3:55 ` Grant Grundler
2006-12-07 3:55 ` Grant Grundler
2006-12-10 7:25 ` Grant Grundler
2006-12-15 17:02 ` Greg KH
2006-12-15 17:02 ` Greg KH
2006-12-18 7:11 ` Grant Grundler
2006-12-18 7:11 ` Grant Grundler
2006-12-22 19:46 ` Randy Dunlap
2006-12-22 19:46 ` Randy Dunlap
2006-12-22 21:52 ` Stefan Richter
2006-12-22 21:52 ` Stefan Richter
2006-12-24 6:11 ` Grant Grundler
2006-12-24 6:07 ` [PATCH] Update Documentation/pci.txt v7 Grant Grundler
2006-12-24 19:16 ` Randy Dunlap
2006-12-25 7:59 ` Grant Grundler [this message]
2006-12-25 8:06 ` Grant Grundler
2006-12-25 8:08 ` Grant Grundler
2007-01-02 21:45 ` Greg KH
2007-01-03 7:15 ` Grant Grundler
2006-12-25 9:04 ` Kenji Kaneshige
2007-01-16 22:26 ` patch pci-rework-documentation-pci.txt.patch added to gregkh-2.6 tree gregkh
2007-01-17 9:10 ` Jiri Slaby
2007-01-17 19:21 ` Greg KH
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=20061225075912.GA32499@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=randy.dunlap@oracle.com \
--cc=seto.hidetoshi@jp.fujitsu.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.