All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Nadim Almas <nadim.902@gmail.com>, Greg KH <gregkh@linuxfoundation.org>
Cc: thomas.petazzoni@free-electrons.com, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging:fbtft/fb_s6d02a1.c: fixed 80 character line limit coding
Date: Fri, 07 Oct 2016 13:00:09 -0700	[thread overview]
Message-ID: <1475870409.1945.11.camel@perches.com> (raw)
In-Reply-To: <CANQNnfH6=7HCb6A-mEdusHX_JBo6mcii75R0mTKjpgRaiJ0RoQ@mail.gmail.com>

On Sat, 2016-10-08 at 00:25 +0530, Nadim Almas wrote:
> why its seems worst to you i am just removing  "80 character line
> limit coding style"
> for the last 3 months I am trying to submit my first patch but patch
> is not accepted by you by giving reason i can't able to understand
> please help me

Taste in improving code is a difficult thing to acquire,
determine and utilize.

Keep on trying to improve the code and not just in ways
that shut-up brainless tools.

Please consider the difference between your initial patch
and this proposal: https://patchwork.kernel.org/patch/9367167/

Apologies for not cc'ing you as your patch was what caused me
to look at this code at all.


> On Fri, Oct 7, 2016 at 10:37 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Fri, Oct 07, 2016 at 08:43:02AM -0700, Nadim Almas wrote:
> > > style issue
> > > 
> > > Fixed coding style issue
> > 
> > 
> > This does not seem like valid sentances that mean much to me.  Do they
> > to you?
> > 
> > > 
> > > Signed-off-by: Nadim Almas <nadim.902@gmail.com>
> > > ---
> > >  drivers/staging/fbtft/fb_s6d02a1.c | 30 ++++++++++++++++++++----------
> > >  1 file changed, 20 insertions(+), 10 deletions(-)
> > > 
> > > diff --git a/drivers/staging/fbtft/fb_s6d02a1.c b/drivers/staging/fbtft/fb_s6d02a1.c
> > > index 774b0ff..bc0c48f 100644
> > > --- a/drivers/staging/fbtft/fb_s6d02a1.c
> > > +++ b/drivers/staging/fbtft/fb_s6d02a1.c
> > > @@ -30,20 +30,27 @@ static int default_init_sequence[] = {
> > > 
> > >       -1, 0xfc, 0x5a, 0x5a,
> > > 
> > > -     -1, 0xfa, 0x02, 0x1f, 0x00, 0x10, 0x22, 0x30, 0x38, 0x3A, 0x3A, 0x3A, 0x3A, 0x3A, 0x3d, 0x02, 0x01,
> > > +     -1, 0xfa, 0x02, 0x1f, 0x00, 0x10, 0x22, 0x30, 0x38, 0x3A, 0x3A, 0x3A,
> > > +                                             0x3A, 0x3A, 0x3d, 0x02, 0x01,
> > 
> > 
> > This looks worse to me now, remember, checkpatch.pl is a "hint", not a
> > hard-and-fast-rule.  Use it wisely.

      reply	other threads:[~2016-10-07 20:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-07 15:43 [PATCH] Staging:fbtft/fb_s6d02a1.c: fixed 80 character line limit coding Nadim Almas
2016-10-07 17:07 ` Greg KH
2016-10-07 18:55   ` Nadim Almas
2016-10-07 20:00     ` Joe Perches [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=1475870409.1945.11.camel@perches.com \
    --to=joe@perches.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nadim.902@gmail.com \
    --cc=thomas.petazzoni@free-electrons.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.