The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] slimbus: fix kerneldoc comments
Date: Thu, 20 Jun 2019 10:46:23 +0200	[thread overview]
Message-ID: <20190620084623.GA20943@kroah.com> (raw)
In-Reply-To: <20190620081129.4721-2-srinivas.kandagatla@linaro.org>

On Thu, Jun 20, 2019 at 09:11:27AM +0100, Srinivas Kandagatla wrote:
> From: Jonathan Corbet <corbet@lwn.net>
> 
> The kerneldoc comments in drivers/slimbus/stream.c were not properly
> formatted, leading to a distinctly unsatisfying "no structured comments
> found" warning in the docs build.  Sprinkle some asterisks around so that
> the comments will be properly recognized.
> 
> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
> ---
>  drivers/slimbus/stream.c | 12 ++++++------
>  1 file changed, 6 insertions(+), 6 deletions(-)

Turns out this was already in my tree :)

Also, when sending out patches, be sure to cc: the authors, no need to
suppress that in git send-email.

thanks,

greg k-h

  reply	other threads:[~2019-06-20  8:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-20  8:11 [PATCH 0/3] drivers: slimbus: patches for 5.3 Srinivas Kandagatla
2019-06-20  8:11 ` [PATCH 1/3] slimbus: fix kerneldoc comments Srinivas Kandagatla
2019-06-20  8:46   ` Greg KH [this message]
2019-06-20  8:47     ` Srinivas Kandagatla
2019-06-20  8:11 ` [PATCH 2/3] slimbus: remove redundant dev_err message Srinivas Kandagatla
2019-06-20  8:11 ` [PATCH 3/3] slimbus: core: generate uevent for non-dt only Srinivas Kandagatla

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=20190620084623.GA20943@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srinivas.kandagatla@linaro.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