public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Yacine Belkadi <yacine.belkadi.1@gmail.com>
Cc: "Alan Stern" <stern@rowland.harvard.edu>,
	"Jiri Kosina" <jkosina@suse.cz>,
	"Sarah Sharp" <sarah.a.sharp@linux.intel.com>,
	"Kevin Hilman" <khilman@linaro.org>,
	"Alexey Khoroshilov" <khoroshilov@ispras.ru>,
	"Thomas Renninger" <trenn@suse.de>,
	"Hannes Reinecke" <hare@suse.de>,
	"Lan Tianyu" <tianyu.lan@intel.com>,
	"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
	"Ming Lei" <ming.lei@canonical.com>,
	"Tülin İzer" <tulinizer@gmail.com>,
	"Sachin Kamat" <sachin.kamat@linaro.org>,
	"Johan Hovold" <jhovold@gmail.com>, "Kay Sievers" <kay@vrfy.org>,
	"Julius Werner" <jwerner@chromium.org>,
	"Yuanhan Liu" <yliu.null@gmail.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH] usb: fix some scripts/kernel-doc warnings
Date: Mon, 5 Aug 2013 05:29:19 +0800	[thread overview]
Message-ID: <20130804212919.GA10623@kroah.com> (raw)
In-Reply-To: <51FEB410.6080909@gmail.com>

On Sun, Aug 04, 2013 at 10:05:36PM +0200, Yacine Belkadi wrote:
> On 08/03/2013 05:29 AM, Greg Kroah-Hartman wrote:
> > On Fri, Aug 02, 2013 at 08:10:04PM +0200, Yacine Belkadi wrote:
> >> When building the htmldocs (in verbose mode), scripts/kernel-doc reports the
> >> following type of warnings:
> >>
> >> Warning(drivers/usb/core/usb.c:76): No description found for return value of
> >> 'usb_find_alt_setting'
> >>
> >> Fix them by:
> >> - adding some missing descriptions of return values
> >> - using "Return" sections for those descriptions
> >>
> >> Signed-off-by: Yacine Belkadi <yacine.belkadi.1@gmail.com>
> >> ---
> >>
> >>  Applied to b3a3a9c441e2c8f6b6760de9331023a7906a4ac6
> > 
> > What does this line mean?
> 
> It's the commit on which I created and applied the patch:
> 
> commit b3a3a9c441e2c8f6b6760de9331023a7906a4ac6
> Merge: a582e5f e70e78e
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> Date:   Mon Jul 22 19:07:24 2013 -0700

Odd, I've never seen anyone use that before.  It's really not needed, so
you don't have to do that in the future.

thanks,

greg k-h

  reply	other threads:[~2013-08-04 21:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-02 18:10 [PATCH] usb: fix some scripts/kernel-doc warnings Yacine Belkadi
2013-08-03  3:29 ` Greg Kroah-Hartman
2013-08-04 20:05   ` Yacine Belkadi
2013-08-04 21:29     ` Greg Kroah-Hartman [this message]
2013-08-05 18:36       ` Yacine Belkadi
2013-08-05 22:28         ` Greg Kroah-Hartman
2013-08-06 17:36           ` Yacine Belkadi

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=20130804212919.GA10623@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bigeasy@linutronix.de \
    --cc=hare@suse.de \
    --cc=jhovold@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=jwerner@chromium.org \
    --cc=kay@vrfy.org \
    --cc=khilman@linaro.org \
    --cc=khoroshilov@ispras.ru \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=ming.lei@canonical.com \
    --cc=sachin.kamat@linaro.org \
    --cc=sarah.a.sharp@linux.intel.com \
    --cc=stern@rowland.harvard.edu \
    --cc=tianyu.lan@intel.com \
    --cc=trenn@suse.de \
    --cc=tulinizer@gmail.com \
    --cc=yacine.belkadi.1@gmail.com \
    --cc=yliu.null@gmail.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