All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Nikolay Kyx <knv418@gmail.com>
Cc: sergiu.cuciurean@analog.com, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: kpc2000: code style: fix alignment issues
Date: Thu, 18 Feb 2021 21:52:24 +0100	[thread overview]
Message-ID: <YC7TiCzbB+4ppzdk@kroah.com> (raw)
In-Reply-To: <20210218202814.14204-1-knv418@gmail.com>

On Thu, Feb 18, 2021 at 11:28:14PM +0300, Nikolay Kyx wrote:
> kpc2000_i2c.c:
> fix WARNING: line length of 124 exceeds 100 columns
> fix CHECK: Alignment should match open parenthesis
> 
> kpc2000_spi.c:
> fix CHECK: Alignment should match open parenthesis

This changelog is a bit odd.

Please read the section entitled "The canonical patch format" in the
kernel file, Documentation/SubmittingPatches for what is needed in order
to properly describe the change.

thanks,

greg k-h

  reply	other threads:[~2021-02-18 20:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-18 20:28 [PATCH] staging: kpc2000: code style: fix alignment issues Nikolay Kyx
2021-02-18 20:52 ` Greg KH [this message]
2021-02-19  8:04   ` [PATCH v2] " Nikolay Kyx
2021-02-19  8:26     ` Greg KH
2021-02-19 16:34       ` [PATCH v3 01/02] " Nikolay Kyx
2021-02-21 13:03         ` Greg KH
2021-02-21 13:22           ` [PATCH v4 01/02] staging: kpc2000: code style: match alignment with open parenthesis Nikolay Kyx
2021-02-21 13:22             ` [PATCH v4 02/02] staging: kpc2000: code style: fix line length issue Nikolay Kyx
2021-02-19 16:34       ` [PATCH v3 02/02] staging: kpc2000: code style: fix alignment issues Nikolay Kyx

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=YC7TiCzbB+4ppzdk@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=knv418@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sergiu.cuciurean@analog.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.