LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Gaurav Dhingra <gauravdhingra.gxyd@gmail.com> To: Viresh Kumar <viresh.kumar@linaro.org>, Mark Greer <mgreer@animalcreek.com> Cc: Johan Hovold <johan@kernel.org>, Alex Elder <elder@kernel.org>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org> Subject: Re: [PATCH] staging: greybus: Fix warning to limit chars per line Date: Fri, 6 Apr 2018 15:47:18 +0530 [thread overview] Message-ID: <4ef1ceb1-395d-753f-1ea2-9affcf682147@gmail.com> (raw) In-Reply-To: <CAOh2x==-Ayr40WhMNmABVEjaoFfSwQfyN8SH07mzmZTicLBh-A@mail.gmail.com> Hi, Thanks for reviewing the patch. On Friday 06 April 2018 10:52 AM, Viresh Kumar wrote: > On Fri, Apr 6, 2018 at 3:49 AM, Mark Greer <mgreer@animalcreek.com> wrote: >> On Wed, Apr 04, 2018 at 12:02:46AM +0530, Gaurav Dhingra wrote: >>> Wrap comment to fix warning "prefer a maximum 75 chars per line" >>> >>> Signed-off-by: Gaurav Dhingra <gauravdhingra.gxyd@gmail.com> >>> --- >>> drivers/staging/greybus/audio_codec.h | 4 +++- >>> 1 file changed, 3 insertions(+), 1 deletion(-) >>> >>> diff --git a/drivers/staging/greybus/audio_codec.h b/drivers/staging/greybus/audio_codec.h >>> index a1d5440..01838d9 100644 >>> --- a/drivers/staging/greybus/audio_codec.h >>> +++ b/drivers/staging/greybus/audio_codec.h >>> @@ -23,7 +23,9 @@ enum { >>> NUM_CODEC_DAIS, >>> }; >>> >>> -/* device_type should be same as defined in audio.h (Android media layer) */ >>> +/* device_type should be same as defined in audio.h > This isn't the right way to write a multi-line comment. It should be like: > > /* > * XXXX > * XXXX > */ I sent in an updated patchset. Though I forgot to add viresh.kumar@linaro.org to "To" in mail. I tried to follow instructions described on https://kernelnewbies.org/FirstKernelPatch for updating my patch. Do you think I followed the instructions correctly? I was thinking may be I need to update the already sent patch by adding *new commit* to my already existing commit on that git branch, but instead I tried to do what I understood from the website I mentioned above. >>> + * (Android media layer) >>> + */ >>> enum { >>> GBAUDIO_DEVICE_NONE = 0x0, >>> /* reserved bits */ >>> -- >>> 1.9.1 >> Hi Gaurav. >> >> Thank you for the patch, it looks fine to me. >> >> Reviewed-by: Mark Greer <mgreer@animalcreek.com> -- Gaurav Dhingra (sent from Thunderbird email client)
next prev parent reply other threads:[~2018-04-06 10:17 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-04-03 18:32 [PATCH] staging: greybus: Fix warning to limit chars per line Gaurav Dhingra 2018-04-05 7:17 ` Gaurav Dhingra 2018-04-05 12:37 ` Greg KH 2018-04-05 22:19 ` Mark Greer 2018-04-06 5:22 ` Viresh Kumar 2018-04-06 10:17 ` Gaurav Dhingra [this message] 2018-04-06 10:25 ` Viresh Kumar 2018-04-06 10:26 ` Viresh Kumar 2018-04-06 10:29 ` Gaurav Dhingra 2018-04-06 16:01 ` Mark Greer
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=4ef1ceb1-395d-753f-1ea2-9affcf682147@gmail.com \ --to=gauravdhingra.gxyd@gmail.com \ --cc=elder@kernel.org \ --cc=gregkh@linuxfoundation.org \ --cc=johan@kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mgreer@animalcreek.com \ --cc=viresh.kumar@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: linkBe 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; as well as URLs for NNTP newsgroup(s).