mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] slimbus: fix kerneldoc comments
Date: Thu, 20 Jun 2019 09:47:49 +0100	[thread overview]
Message-ID: <c6c172db-3eec-8f4e-ac32-0b7cb487c5e3@linaro.org> (raw)
In-Reply-To: <20190620084623.GA20943@kroah.com>



On 20/06/2019 09:46, Greg KH wrote:
> 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 :)
>
Ah, I should have rebased it on top of char-misc!


> Also, when sending out patches, be sure to cc: the authors, no need to
> suppress that in git send-email.
> 
Sure, I will keep that in mind!

thanks,
srini
> thanks,
> 
> greg k-h
> 

  reply	other threads:[~2019-06-20  8:47 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
2019-06-20  8:47     ` Srinivas Kandagatla [this message]
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=c6c172db-3eec-8f4e-ac32-0b7cb487c5e3@linaro.org \
    --to=srinivas.kandagatla@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.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 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®