linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: sfr@canb.auug.org.au, david@fromorbit.com,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for December 18 (patch: kernel-doc notation)
Date: Mon, 22 Dec 2008 14:49:45 -0800	[thread overview]
Message-ID: <20081222144945.8ef2748e.akpm@linux-foundation.org> (raw)
In-Reply-To: <20081218161437.fe2d2675.randy.dunlap@oracle.com>

On Thu, 18 Dec 2008 16:14:37 -0800
Randy Dunlap <randy.dunlap@oracle.com> wrote:

> fs/inode.c and mm/filemap.c need kernel-doc fixes.
> 
> What tree were these merged into for linux-next?

I use git-blame.

> How do I get these doc fixes merged?  (2 patches below)
> 
> ---
> 
> From: Randy Dunlap <randy.dunlap@oracle.com>
> 
> Fix fs/inode.c kernel-doc function parameters:
> 
> Warning(linux-next-20081218//fs/inode.c:120): No description found for parameter 'sb'
> Warning(linux-next-20081218//fs/inode.c:120): No description found for parameter 'inode'
> Warning(linux-next-20081218//fs/inode.c:588): No description found for parameter 'sb'
> Warning(linux-next-20081218//fs/inode.c:588): No description found for parameter 'inode'
> 

>From the XFS tree:

commit 2cb1599f9b2ecdd7a9e59feeee647eb258966839
Author:     David Chinner <david@fromorbit.com>
AuthorDate: Thu Oct 30 17:32:23 2008 +1100
Commit:     Lachlan McIlroy <lachlan@redback.melbourne.sgi.com>
CommitDate: Thu Oct 30 17:32:23 2008 +1100

    Inode: Allow external initialisers


> ---
> 
> From: Randy Dunlap <randy.dunlap@oracle.com>
> 
> Fix mm/filemap.c functions' kernel-doc:
> 
> Warning(/local/linsrc/linux-next-20081218//mm/filemap.c:575): No description found for parameter 'page'
> Warning(/local/linsrc/linux-next-20081218//mm/filemap.c:575): No description found for parameter 'waiter'
> Warning(/local/linsrc/linux-next-20081218//mm/filemap.c:2348): No description found for parameter 'mapping'
> Warning(/local/linsrc/linux-next-20081218//mm/filemap.c:2348): No description found for parameter 'index'
> Warning(/local/linsrc/linux-next-20081218//mm/filemap.c:2348): No description found for parameter 'source'
> 
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> cc: Dave Chinner <david@fromorbit.com>

That's no longer in linux-next.  I'd guess it was from the fs-cache
patches.

      parent reply	other threads:[~2008-12-22 22:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-18 12:06 linux-next: Tree for December 18 Stephen Rothwell
2008-12-18 17:21 ` linux-next: Tree for December 18 (slow-work) Randy Dunlap
2008-12-18 17:45   ` David Howells
2008-12-18 17:25 ` linux-next: Tree for December 18 (fscache) Randy Dunlap
2008-12-18 17:47   ` David Howells
2008-12-18 23:57 ` linux-next: Tree for December 18 (irq.h documentation) Randy Dunlap
2008-12-19  0:33   ` Yinghai Lu
2008-12-19  0:45     ` Randy Dunlap
2008-12-19  0:57     ` Yinghai Lu
2008-12-19  1:00       ` Randy Dunlap
2008-12-19  0:14 ` linux-next: Tree for December 18 (patch: kernel-doc notation) Randy Dunlap
2008-12-19 10:39   ` Dave Chinner
2008-12-22 22:49   ` Andrew Morton [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=20081222144945.8ef2748e.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=david@fromorbit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=sfr@canb.auug.org.au \
    /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).