From: Dhiraj Sharma <dhiraj.sharma0024@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
stern@rowland.harvard.edu, arnd@arndb.de, jrdr.linux@gmail.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org
Subject: Re: [PATCH] media: usbvision: fixed coding style
Date: Tue, 28 Jul 2020 21:14:24 +0530 [thread overview]
Message-ID: <CAPRy4h1Xs1JpQinnWm04dOi07Ch0RLL0U4Z5DDCKHmombXE0sA@mail.gmail.com> (raw)
In-Reply-To: <20200728145419.GA3537020@kroah.com>
Sorry, I didn't realize that I committed a mistake by not replying to
all. It was an accidental mistake which will not be committed in
future now.
>
> That is not needed in a changelog text.
>
Alright Sir.
> Neither is this, please be specific about what you have fixed. My bot
> should kick in soon with more specifics...
Sir there were checkpatch.pl styling issues and I fixed them all
together, so should I write a proper changelog as what all I fixed i.e
errors and warnings thrown by checkpatch.pl
On Tue, Jul 28, 2020 at 8:24 PM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Tue, Jul 28, 2020 at 08:00:04PM +0530, Dhiraj Sharma wrote:
> > As per eudyptula challenge task 10 I had to fix coding styles.
>
> That is not needed in a changelog text.
>
> > Thus I
> > used checkpatch.pl script and fixed a chunk of warnings and few errors.
>
> Neither is this, please be specific about what you have fixed. My bot
> should kick in soon with more specifics...
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2020-07-28 15:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 14:30 [PATCH] media: usbvision: fixed coding style Dhiraj Sharma
2020-07-28 14:54 ` Greg KH
2020-07-28 15:44 ` Dhiraj Sharma [this message]
2020-07-28 15:53 ` Greg KH
2020-07-28 16:43 ` Dhiraj Sharma
2020-07-28 16:58 ` Greg KH
2020-07-28 16:59 ` Dhiraj Sharma
2020-07-28 14:54 ` Greg KH
2020-07-28 15:05 ` Hans Verkuil
2020-07-28 15:47 ` Dhiraj Sharma
2020-07-28 17:39 ` kernel test robot
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=CAPRy4h1Xs1JpQinnWm04dOi07Ch0RLL0U4Z5DDCKHmombXE0sA@mail.gmail.com \
--to=dhiraj.sharma0024@gmail.com \
--cc=arnd@arndb.de \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hverkuil@xs4all.nl \
--cc=jrdr.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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;
as well as URLs for NNTP newsgroup(s).