From: Greg KH <gregkh@linuxfoundation.org>
To: Madhumthia Prabakaran <madhumithabiw@gmail.com>
Cc: forest@alittletooquiet.net, outreachy-kernel@googlegroups.com
Subject: Re: [PATCH v2] Staging: vt6655: Modify comment style for SPDX License Identifier
Date: Wed, 27 Feb 2019 18:33:02 +0100 [thread overview]
Message-ID: <20190227173302.GA16146@kroah.com> (raw)
In-Reply-To: <20190227171022.GA22572@madhuleo>
On Wed, Feb 27, 2019 at 11:10:23AM -0600, Madhumthia Prabakaran wrote:
> On Wed, Feb 27, 2019 at 06:05:14PM +0100, Greg KH wrote:
> > On Wed, Feb 27, 2019 at 10:43:29AM -0600, Madhumthia Prabakaran wrote:
> > > On Wed, Feb 27, 2019 at 03:48:36PM +0100, Greg KH wrote:
> > > > On Tue, Feb 26, 2019 at 03:55:31PM -0600, Madhumitha Prabakaran wrote:
> > > > > FIx the warning by changing comment style based on header file type as
> > > > > per License identifier syntax
> > > > >
> > > > > Signed-off-by: Madhumitha Prabakaran <madhumithabiw@gmail.com>
> > > > > ---
> > > > > Changes in v2
> > > > > - Modified subject line and commit log
> > > > >
> > > > > drivers/staging/vt6655/baseband.h | 2 +-
> > > > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > > > >
> > > > > diff --git a/drivers/staging/vt6655/baseband.h b/drivers/staging/vt6655/baseband.h
> > > > > index f2b6a98de2c1..0cc2e07829c5 100644
> > > > > --- a/drivers/staging/vt6655/baseband.h
> > > > > +++ b/drivers/staging/vt6655/baseband.h
> > > > > @@ -1,4 +1,4 @@
> > > > > -* SPDX-License-Identifier: GPL-2.0+ */
> > > > > +/* SPDX-License-Identifier: GPL-2.0+ */
> > > >
> > > > This patch does not apply to my tree :(
> > > >
> > >
> > >
> > > I didn't understand why it doesn't apply to your tree.
> > >
> >
> > Neither do I :)
> >
> > Please try rebasing your patch on the top of my staging-testing branch
> > and see if that produces a different patch or not. If it does, please
> > resend.
> >
> > thanks,
> >
> > greg k-h
>
>
> I will rebase it and send it again.
>
> Also, I want to make sure whether you got a similar patch with same commit log or not.
I have no idea.
Remember, I get over 1000 emails a day to do something with, I have the
short-term memory of a squirrel and have no idea if someone has sent
something prior to this at all, sorry.
It is your job as a patch submitter to make it as easy as possible for
me to apply patches. Sometimes that requires extra work, and rebasing
patches due to other people's patches colliding with your work. That's
just part of the development process.
thanks,
greg k-h
next prev parent reply other threads:[~2019-02-27 17:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 21:55 [PATCH v2] Staging: vt6655: Modify comment style for SPDX License Identifier Madhumitha Prabakaran
2019-02-27 14:48 ` Greg KH
2019-02-27 16:43 ` Madhumthia Prabakaran
2019-02-27 17:05 ` Greg KH
2019-02-27 17:10 ` Madhumthia Prabakaran
2019-02-27 17:33 ` Greg KH [this message]
2019-02-27 17:42 ` Madhumthia Prabakaran
2019-02-27 19:46 ` [Outreachy kernel] " Julia Lawall
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=20190227173302.GA16146@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=forest@alittletooquiet.net \
--cc=madhumithabiw@gmail.com \
--cc=outreachy-kernel@googlegroups.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 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.