From: Grant Grundler <grundler@parisc-linux.org>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: linux-pci@atrey.karlin.mff.cuni.cz,
Matti Linnanvuori <mattilinnanvuori@yahoo.com>,
Grant Grundler <grundler@parisc-linux.org>,
gregkh@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [patch v2] doc: DMA-mapping.txt has undeclared variables [Bug 10397]
Date: Wed, 9 Apr 2008 12:45:32 -0600 [thread overview]
Message-ID: <20080409184532.GG1624@colo.lackof.org> (raw)
In-Reply-To: <200804070905.51499.jbarnes@virtuousgeek.org>
On Mon, Apr 07, 2008 at 09:05:51AM -0700, Jesse Barnes wrote:
> On Monday, April 07, 2008 9:01 am Matti Linnanvuori wrote:
> > From: Matti Linnanvuori <mattilinnanvuori@yahoo.com>
> >
> > Fix undeclared variables in code examples.
> > Consistently use pdev as the variable of type struct pci_dev *.
> > Bug 10397.
>
> I think Grant's comment still stands, "fix undeclared variables" isn't an
> accurate description of what you're doing here...
Yes, please just drop the first sentence. The second sentence is sufficient.
> That said, the patch itself looks fine to me, if a bit pedantic. The compiler
> will catch any mismatched arguments in this case, and the rest of the
> documentation is pretty clear that these routines take struct pci_dev not
> struct device, so I'd be inclined to just leave it the way it is to avoid
> churn.
I think it's a good habit to use "pdev" in device drivers and would
like the documentation to incorporate that.
I'm ok with the churn since it's not conflicting with anything else AFAIK.
thanks,
grant
next prev parent reply other threads:[~2008-04-09 18:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 16:01 Matti Linnanvuori
2008-04-07 16:05 ` Jesse Barnes
2008-04-09 18:45 ` Grant Grundler [this message]
2008-04-23 17:58 ` Jesse Barnes
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=20080409184532.GG1624@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=gregkh@suse.de \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=mattilinnanvuori@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome