From: Javier Martinez <javiermlinux@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: octeon-usb: octeon-hcd.c: style fix line length warning
Date: Wed, 13 Jun 2018 16:59:55 -0400 [thread overview]
Message-ID: <20180613205955.GA16029@javier-Z97X> (raw)
In-Reply-To: <20180613205255.GA14313@kroah.com>
On Wed, Jun 13, 2018 at 10:52:55PM +0200, Greg KH wrote:
> On Wed, Jun 13, 2018 at 04:40:15PM -0400, Javier Martinez wrote:
> > Checkpatch.pl issued a warning in the top of the commment within
> > octeon-hcd.c. This is a simple style fix for that.
> >
> > Signed-off-by: Javier Martinez <javiermlinux@gmail.com>
> > ---
> > drivers/staging/octeon-usb/octeon-hcd.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/staging/octeon-usb/octeon-hcd.c b/drivers/staging/octeon-usb/octeon-hcd.c
> > index cded30f145aa..768b0148f3d5 100644
> > --- a/drivers/staging/octeon-usb/octeon-hcd.c
> > +++ b/drivers/staging/octeon-usb/octeon-hcd.c
> > @@ -1,5 +1,5 @@
> > /*
> > - * This file is subject to the terms and conditions of the GNU General Public
> > + * This file is subject to the terms and conditions of the GPL
> > * License. See the file "COPYING" in the main directory of this archive
>
> The grammer is now incorrect :(
>
> Shouldn't we just have a SPDX line at the top here and this whole boiler
> plate text be removed?
>
> thanks,
>
> greg k-h
Sure, will get right to it. I am actually newbie to all this.
I watched your tutorial on youtube when you were at FOSDEM,
Huge help, thank you for that.
prev parent reply other threads:[~2018-06-13 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 20:40 [PATCH] Staging: octeon-usb: octeon-hcd.c: style fix line length warning Javier Martinez
2018-06-13 20:52 ` Greg KH
2018-06-13 20:59 ` Javier Martinez [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=20180613205955.GA16029@javier-Z97X \
--to=javiermlinux@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.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.