All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dhiraj Sharma <dhiraj.sharma0024@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org, arnd@arndb.de,
	linux-kernel@vger.kernel.org, Hans Verkuil <hverkuil@xs4all.nl>,
	stern@rowland.harvard.edu, jrdr.linux@gmail.com,
	linux-media@vger.kernel.org
Subject: Re: [PATCH] media: usbvision: fixed coding style
Date: Tue, 28 Jul 2020 22:29:58 +0530	[thread overview]
Message-ID: <CAPRy4h1byz5_r0GdEagvx6Sini3P3uA5Mm4K6AdmM4wHjk+y9A@mail.gmail.com> (raw)
In-Reply-To: <20200728165820.GA42656@kroah.com>

Alright sorry, I will ignore this patch and will commit the new patch
in another file.


On Tue, Jul 28, 2020 at 10:28 PM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Tue, Jul 28, 2020 at 10:13:22PM +0530, Dhiraj Sharma wrote:
> > > As the bot said, only do one type of thing per patch, and "fix all
> > > checkpatch errors/warnings" is not one type of thing.
> >
> > So should I send a fresh patch with minimal fixes? instead of replying
> > to this mail with [PATCH 01]
>
> Why are you ignoring what Hans said?

WARNING: multiple messages have this Message-ID (diff)
From: Dhiraj Sharma <dhiraj.sharma0024@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org, arnd@arndb.de,
	linux-kernel@vger.kernel.org, Hans Verkuil <hverkuil@xs4all.nl>,
	stern@rowland.harvard.edu, jrdr.linux@gmail.com,
	linux-media@vger.kernel.org
Subject: Re: [PATCH] media: usbvision: fixed coding style
Date: Tue, 28 Jul 2020 22:29:58 +0530	[thread overview]
Message-ID: <CAPRy4h1byz5_r0GdEagvx6Sini3P3uA5Mm4K6AdmM4wHjk+y9A@mail.gmail.com> (raw)
In-Reply-To: <20200728165820.GA42656@kroah.com>

Alright sorry, I will ignore this patch and will commit the new patch
in another file.


On Tue, Jul 28, 2020 at 10:28 PM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Tue, Jul 28, 2020 at 10:13:22PM +0530, Dhiraj Sharma wrote:
> > > As the bot said, only do one type of thing per patch, and "fix all
> > > checkpatch errors/warnings" is not one type of thing.
> >
> > So should I send a fresh patch with minimal fixes? instead of replying
> > to this mail with [PATCH 01]
>
> Why are you ignoring what Hans said?
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

  reply	other threads:[~2020-07-28 17:00 UTC|newest]

Thread overview: 23+ 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:30 ` Dhiraj Sharma
2020-07-28 14:54 ` Greg KH
2020-07-28 14:54   ` Greg KH
2020-07-28 15:44   ` Dhiraj Sharma
2020-07-28 15:44     ` Dhiraj Sharma
2020-07-28 15:53     ` Greg KH
2020-07-28 15:53       ` Greg KH
2020-07-28 16:43       ` Dhiraj Sharma
2020-07-28 16:43         ` Dhiraj Sharma
2020-07-28 16:58         ` Greg KH
2020-07-28 16:58           ` Greg KH
2020-07-28 16:59           ` Dhiraj Sharma [this message]
2020-07-28 16:59             ` Dhiraj Sharma
2020-07-28 14:54 ` Greg KH
2020-07-28 14:54   ` Greg KH
2020-07-28 15:05 ` Hans Verkuil
2020-07-28 15:05   ` Hans Verkuil
2020-07-28 15:47   ` Dhiraj Sharma
2020-07-28 15:47     ` Dhiraj Sharma
2020-07-28 17:39 ` kernel test robot
2020-07-28 17:39   ` kernel test robot
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=CAPRy4h1byz5_r0GdEagvx6Sini3P3uA5Mm4K6AdmM4wHjk+y9A@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 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.