All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li Zhong <zhong@linux.vnet.ibm.com>
To: Wanpeng Li <liwp.linux@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, trivial@kernel.org
Subject: Re: [PATCH][TRIVIAL] Fix comments in mm/memblock.c
Date: Thu, 14 Jun 2012 12:09:24 +0800	[thread overview]
Message-ID: <1339646964.12607.11.camel@ThinkPad-T420> (raw)
In-Reply-To: <20120614035423.GC15262@kernel>

On Thu, 2012-06-14 at 11:54 +0800, Wanpeng Li wrote:
> On Thu, Jun 14, 2012 at 11:47:30AM +0800, Li Zhong wrote:
> >Make the parameter names in comments consistent with the actual ones
> >used in the function.
> >
> >Signed-off-by: Li Zhong <zhong@linux.vnet.ibm.com>
> >---
> > mm/memblock.c |    6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> 
> Hi Li Zhong,
> 
> I have already send a path to fix this issues. 
> title is "mm:fix kernel-doc warnings"

Ah, ok. 

Sorry for the noise ...

> 
> Regards,
> Wanpeng Li
> 
> >
> >diff --git a/mm/memblock.c b/mm/memblock.c
> >index 952123e..76cb09f 100644
> >--- a/mm/memblock.c
> >+++ b/mm/memblock.c
> >@@ -540,9 +540,9 @@ int __init_memblock memblock_reserve(phys_addr_t
> >base, phys_addr_t size)
> >  * __next_free_mem_range - next function for for_each_free_mem_range()
> >  * @idx: pointer to u64 loop variable
> >  * @nid: nid: node selector, %MAX_NUMNODES for all nodes
> >- * @p_start: ptr to phys_addr_t for start address of the range, can be
> >%NULL
> >- * @p_end: ptr to phys_addr_t for end address of the range, can be %
> >NULL
> >- * @p_nid: ptr to int for nid of the range, can be %NULL
> >+ * @out_start: ptr to phys_addr_t for start address of the range, can
> >be %NULL
> >+ * @out_end: ptr to phys_addr_t for end address of the range, can be %
> >NULL
> >+ * @out_nid: ptr to int for nid of the range, can be %NULL
> >  *
> >  * Find the first free area from *@idx which matches @nid, fill the out
> >  * parameters, and update *@idx for the next iteration.  The lower
> >32bit of
> >-- 
> >1.7.9.5
> >
> >--
> >To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> >the body of a message to majordomo@vger.kernel.org
> >More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >Please read the FAQ at  http://www.tux.org/lkml/
> 



      reply	other threads:[~2012-06-14  4:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14  3:47 [PATCH][TRIVIAL] Fix comments in mm/memblock.c Li Zhong
2012-06-14  3:54 ` Wanpeng Li
2012-06-14  4:09   ` Li Zhong [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=1339646964.12607.11.camel@ThinkPad-T420 \
    --to=zhong@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liwp.linux@gmail.com \
    --cc=trivial@kernel.org \
    /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.