From: Greg KH <gregkh@linuxfoundation.org>
To: Prasant Jalan <prasant.jalan@gmail.com>
Cc: forest@alittletooquiet.net,
Arushi Singhal <arushisinghal19971997@gmail.com>,
devel@driverdev.osuosl.org, johannes.berg@intel.com,
linux-kernel@vger.kernel.org,
Michael Hansen <michael.schacht.hansen@gmail.com>
Subject: Re: [PATCH] staging: vt6656: removed coding style errors
Date: Thu, 23 Mar 2017 10:00:23 +0100 [thread overview]
Message-ID: <20170323090023.GB19222@kroah.com> (raw)
In-Reply-To: <CAOzquK94MPu1CeJwf2pCHCHwv0Y6404sj6Fs5Aga=taDb5=ZgQ@mail.gmail.com>
On Thu, Mar 23, 2017 at 01:55:31PM +0530, Prasant Jalan wrote:
> On Thu, Mar 23, 2017 at 1:02 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Wed, Mar 22, 2017 at 09:39:24PM +0530, Prasant Jalan wrote:
> > > The patch replaces spaces with tabs as required by kernel coding
> > > standards.
> > >
> > > Signed-off-by: Prasant Jalan <prasant.jalan@gmail.com>
> > > ---
> > > drivers/staging/vt6656/rxtx.c | 40 ++++++++++++++++++++++------------------
> > > 1 file changed, 22 insertions(+), 18 deletions(-)
> >
> > As this seems to be identical to the previous patch you sent, and I
> > don't see a difference in the changelog comments, I'm dropping it from
> > my queue. Please note that all pending patches from you have been
> > dropped, please resend all of them that still apply.
> >
>
> Hi Greg,
>
> I'm sorry that I sent a bad patch again and thanks so much for your comments.
>
> Should I be sending the patch with more verbose commit message?
That's not what I asked for at all, please go read my prior emails to
you :(
greg k-h
prev parent reply other threads:[~2017-03-23 9:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 16:09 [PATCH] staging: vt6656: removed coding style errors Prasant Jalan
2017-03-23 7:32 ` Greg KH
2017-03-23 8:25 ` Prasant Jalan
2017-03-23 9:00 ` Greg KH [this message]
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=20170323090023.GB19222@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arushisinghal19971997@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=forest@alittletooquiet.net \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.schacht.hansen@gmail.com \
--cc=prasant.jalan@gmail.com \
/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