public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] kernel-doc: ignore kmemcheck_bitfield_begin/end
Date: Sat, 20 Jun 2009 13:38:14 +0200	[thread overview]
Message-ID: <20090620113814.GA32507@uranus.ravnborg.org> (raw)
In-Reply-To: <4A398BFF.2090308@oracle.com>

On Wed, Jun 17, 2009 at 05:36:15PM -0700, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
> 
> Teach kernel-doc to ignore kmemcheck_bitfield_{begin,end} sugar
> so that it won't generate warnings like this:
> 
> Warning(include/net/sock.h:297): No description found for parameter 'kmemcheck_bitfield_begin(flags)'
> Warning(include/net/sock.h:297): No description found for parameter 'kmemcheck_bitfield_end(flags)'
> 
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>

Applied.

	Sam

      reply	other threads:[~2009-06-20 11:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-18  0:36 [PATCH] kernel-doc: ignore kmemcheck_bitfield_begin/end Randy Dunlap
2009-06-20 11:38 ` Sam Ravnborg [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=20090620113814.GA32507@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --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