linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Robert N <robert.nachlinger@gmail.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	Robert Nachlinger <robert.nachlinger@googlemail.com>
Subject: Re: [PATCH] Staging: gdm724x: fix space before comma coding style issue in gdm_mux.c
Date: Sat, 20 Dec 2014 09:12:16 -0800	[thread overview]
Message-ID: <20141220171216.GA24340@kroah.com> (raw)
In-Reply-To: <CABdSh179apawgBKm9=2vBaxVBPTemz4SPhDcgf_2kwk7rsn2oA@mail.gmail.com>

On Sat, Dec 20, 2014 at 12:51:00PM +0100, Robert N wrote:
> I already sent you the patch line-wrapped at column 69, so it says:
> 
> > This is a patch to the gdm_mux.c file that fixes a space before comma
> > coding style issue found by the checkpatch.pl tool.
> 
> Do i have to wrap it exactly at column 72? That would break a word:
> 
> > This is a patch to the gdm_mux.c file that fixes a space before comma co
> > ding style issue found by the checkpatch.pl tool.

Of course not, use a "sane" editor that wraps at a word boundry please.

thanks,

greg k-h

  parent reply	other threads:[~2014-12-20 17:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-18 16:46 [PATCH] Staging: gdm724x: fix space before comma coding style issue in gdm_mux.c Robert Nachlinger
2014-12-18 16:52 ` Greg KH
2014-12-19 22:58 ` Greg KH
     [not found]   ` <CABdSh179apawgBKm9=2vBaxVBPTemz4SPhDcgf_2kwk7rsn2oA@mail.gmail.com>
2014-12-20 17:12     ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-12-21 10:44 Robert Nachlinger
2015-01-17 22:57 ` Greg KH
2014-12-18 16:57 Robert Nachlinger
2014-12-18 14:09 Robert Nachlinger

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=20141220171216.GA24340@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robert.nachlinger@gmail.com \
    --cc=robert.nachlinger@googlemail.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).