From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Dmitry Baryshkov <dbaryshkov@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
mingo@elte.hu
Subject: Re: dma-coherent: add documentation to new interfaces
Date: Thu, 31 Jul 2008 12:49:35 -0700 [thread overview]
Message-ID: <200807311249.36071.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <20080730072811.902b55e0.randy.dunlap@oracle.com>
On Wednesday, July 30, 2008 7:28 am Randy Dunlap wrote:
> On Wed, 30 Jul 2008 14:46:50 +0400 Dmitry Baryshkov wrote:
> > On Tue, Jul 29, 2008 at 01:17:57PM -0700, Randy Dunlap wrote:
> > > On Tue, 29 Jul 2008 03:01:07 GMT Linux Kernel Mailing List wrote:
> > > > Gitweb:
> > > > http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;
> > > >a=commit;h=b6d4f7e3ef25beb8c658c97867d98883e69dc544 Commit:
> > > > b6d4f7e3ef25beb8c658c97867d98883e69dc544
> > > > Parent: 8fa8b9fbab90c74139e8e868fe5b30b6a9f6be65
> > > > Author: Dmitry Baryshkov <dbaryshkov@gmail.com>
> > > > AuthorDate: Sun Jul 20 15:01:10 2008 +0400
> > > > Committer: Ingo Molnar <mingo@elte.hu>
> > > > CommitDate: Sun Jul 20 21:22:00 2008 +0200
> > > >
> > > > dma-coherent: add documentation to new interfaces
> > >
> > > Hi,
> > > Please fix these to be proper kernel-doc notation, as described in
> > > Documentation/kernel-doc-nano-HOWTO.txt ...
> >
> > Please consider this patch:
>
> Looks good. Thanks.
>
> Jesse or Ingo: will one of you merge this, please?
Just pushed it into my for-linus branch. I added your "Acked-by" too, thanks
for checking it out.
Jesse
prev parent reply other threads:[~2008-07-31 19:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200807290301.m6T317GG021226@hera.kernel.org>
2008-07-29 20:17 ` Randy Dunlap
2008-07-30 10:46 ` Dmitry Baryshkov
2008-07-30 14:28 ` Randy Dunlap
2008-07-31 19:49 ` Jesse Barnes [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=200807311249.36071.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=dbaryshkov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=randy.dunlap@oracle.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
all inboxes | Powered by JetHome®