mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Moyer <jmoyer@redhat.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>, axboe <axboe@kernel.dk>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v2] block: fix blk-core.c kernel-doc warning
Date: Mon, 02 Nov 2015 08:59:45 -0500	[thread overview]
Message-ID: <x494mh4sdri.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <56341B10.9030106@infradead.org> (Randy Dunlap's message of "Fri, 30 Oct 2015 18:36:16 -0700")

Randy Dunlap <rdunlap@infradead.org> writes:

> From: Randy Dunlap <rdunlap@infradead.org>
>
> Fix kernel-doc warning in blk-core.c:
>
> Warning(..//block/blk-core.c:1549): No description found for parameter 'same_queue_rq'
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Jeff Moyer <jmoyer@redhat.com>
> Cc: Jens Axboe <axboe@kernel.dk>

Thanks, Randy.

Reviewed-by: Jeff Moyer <jmoyer@redhat.com>

> ---
>  block/blk-core.c |    3 +++
>  1 file changed, 3 insertions(+)
>
> --- lnx-43-rc7.orig/block/blk-core.c
> +++ lnx-43-rc7/block/blk-core.c
> @@ -1529,6 +1529,9 @@ bool bio_attempt_front_merge(struct requ
>   * @q: request_queue new bio is being queued at
>   * @bio: new bio being queued
>   * @request_count: out parameter for number of traversed plugged requests
> + * @same_queue_rq: pointer to &struct request that gets filled in when
> + * another request associated with @q is found on the plug list
> + * (optional, may be %NULL)
>   *
>   * Determine whether @bio being queued on @q can be merged with a request
>   * on %current's plugged list.  Returns %true if merge was successful,

      reply	other threads:[~2015-11-02 13:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-31  1:36 Randy Dunlap
2015-11-02 13:59 ` Jeff Moyer [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=x494mh4sdri.fsf@segfault.boston.devel.redhat.com \
    --to=jmoyer@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.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 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®