linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Scott Matheina <scott@matheina.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: thomas.petazzoni@free-electrons.com, noralf@tronnes.org,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] fix code alignment with open parenthesis
Date: Mon, 19 Dec 2016 18:29:53 -0600	[thread overview]
Message-ID: <87d307a0-8003-e722-ec31-3c1c083e9613@matheina.com> (raw)
In-Reply-To: <20161219063547.GB5814@kroah.com>



On 12/19/2016 12:35 AM, Greg KH wrote:
> On Sun, Dec 18, 2016 at 11:47:30AM -0600, Scott Matheina wrote:
>> These changes where identified by checkpatch.pl as needed changes to
>> align the code with the linux development coding style. The several
>> lines of text where aligned with the precending parenthesis.
>>
>> Signed-off-by: Scott Matheina <scott@matheina.com>
>>
>>   Changes to be committed:
>> 	modified:   drivers/staging/fbtft/fb_agm1264k-fl.c
I'll remove the above text after signed-off-by and resubmit, honestly 
it's been
over a year since I submitted a patch so I have to relearn how you want 
them
formatted. Thanks for working with me.
> Why are these lines in the changelog text?

      parent reply	other threads:[~2016-12-20  0:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-18 17:47 [PATCH v2] fix code alignment with open parenthesis Scott Matheina
2016-12-19  6:35 ` Greg KH
2016-12-19 17:44   ` [PATCH] drivers: staging: fbtft: fix checkpatch error and udelay Ozgur Karatas
2017-01-03 15:26     ` Greg KH
2016-12-20  0:29   ` Scott Matheina [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=87d307a0-8003-e722-ec31-3c1c083e9613@matheina.com \
    --to=scott@matheina.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=noralf@tronnes.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).