From: Gaurav Dhingra <gauravdhingra.gxyd@gmail.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: driver-dev <devel@driverdev.osuosl.org>,
Vaibhav Agarwal <vaibhav.sr@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Johan Hovold <johan@kernel.org>,
Mark Greer <mgreer@animalcreek.com>,
greybus-dev@lists.linaro.org
Subject: Re: [PATCH v2] staging: greybus: Fix warning to limit chars per line
Date: Fri, 6 Apr 2018 16:02:40 +0530 [thread overview]
Message-ID: <1bb8c642-a2ba-0c8c-cab9-b4ea408eeedb@gmail.com> (raw)
In-Reply-To: <CAOh2x==TphhhoPVSFdFmFCQr4Ag_+tMzOOW3yp-e++SQcrWggA@mail.gmail.com>
Hi,
On Friday 06 April 2018 03:52 PM, Viresh Kumar wrote:
> On Fri, Apr 6, 2018 at 3:39 PM, Gaurav Dhingra
> <gauravdhingra.gxyd@gmail.com> wrote:
>
> Why did you remove the commit log? You had the right one in v1.
>
I didn't realize that it would be necessary to add it to this patch set.
I thought you guys will do squashing of the commits (v2 and v1) and
using just one commit message (and will take it from last commit), seems
like I was wrong. Now I've understood it.
>> Signed-off-by: Gaurav Dhingra <gauravdhingra.gxyd@gmail.com>
>> ---
>> Changes in v2:
>> - use correct format for multiline comment
>> ---
>> drivers/staging/greybus/audio_codec.h | 5 ++++-
>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/staging/greybus/audio_codec.h b/drivers/staging/greybus/audio_codec.h
>> index a1d5440..4efd8b3 100644
>> --- a/drivers/staging/greybus/audio_codec.h
>> +++ b/drivers/staging/greybus/audio_codec.h
>> @@ -23,7 +23,10 @@ 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
>> + * (Android media layer)
>> + */
>> enum {
>> GBAUDIO_DEVICE_NONE = 0x0,
>> /* reserved bits */
> This looks ok.
Do I now need to send v3 with these exact changes, since I missed the
'commit log' in this one?
--
Gaurav Dhingra
(sent from Thunderbird email client)
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2018-04-06 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 10:09 [greybus-dev] [PATCH v2] staging: greybus: Fix warning to limit chars per line Gaurav Dhingra
2018-04-06 10:22 ` Viresh Kumar
2018-04-06 10:32 ` Gaurav Dhingra [this message]
2018-04-06 10:35 ` [greybus-dev] " Viresh Kumar
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=1bb8c642-a2ba-0c8c-cab9-b4ea408eeedb@gmail.com \
--to=gauravdhingra.gxyd@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgreer@animalcreek.com \
--cc=vaibhav.sr@gmail.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.