Re: linux-next: Tree for December 18 (patch: kernel-doc notation)

[Andrew Morton]

On Thu, 18 Dec 2008 16:14:37 -0800
Randy Dunlap <randy.dunlap@xxxxxxxxxx> 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@xxxxxxxxxx>
> 
> 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@xxxxxxxxxxxxx>
AuthorDate: Thu Oct 30 17:32:23 2008 +1100
Commit:     Lachlan McIlroy <lachlan@xxxxxxxxxxxxxxxxxxxxxxxxx>
CommitDate: Thu Oct 30 17:32:23 2008 +1100

    Inode: Allow external initialisers


> ---
> 
> From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
> 
> 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@xxxxxxxxxx>
> cc: Dave Chinner <david@xxxxxxxxxxxxx>

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/