All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Michael Mera <dev@michaelmera.com>
Cc: William Hubbs <w.d.hubbs@gmail.com>,
	Chris Brannon <chris@the-brannons.com>,
	Kirk Reiser <kirk@reisers.ca>,
	Samuel Thibault <samuel.thibault@ens-lyon.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] staging: speakup: fix wrong code indent
Date: Fri, 28 Apr 2017 17:52:25 +0200	[thread overview]
Message-ID: <20170428155225.GA18808@kroah.com> (raw)
In-Reply-To: <20170428144326.23397-1-dev@michaelmera.com>

On Fri, Apr 28, 2017 at 11:43:26PM +0900, Michael Mera wrote:
> Fix checkpatch messages:
> ERROR: code indent should use tabs where possible
> WARNING: Block comments should align the * on each line
> 
> Changes:
>   - replace unnecessary multiline comment by a single line comment
>   - change "bit mask" for "bitmask" to have a line shorter than 80
>     characters
> 
> Signed-off-by: Michael Mera <dev@michaelmera.com>
> ---
> 
> v2 -> v3:
>   - add missing changes descriptions
>   - improve patch message to make it more clear what changed

This patch doesn't apply to my tree at all, what tree/branch did you
make it against?

thanks,

greg k-h

  reply	other threads:[~2017-04-28 15:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-28  6:20 [PATCH] staging: speakup: fix wrong code indent Michael Mera
2017-04-28  7:11 ` Greg Kroah-Hartman
2017-04-28  8:46   ` [PATCH v2] " Michael Mera
2017-04-28  9:00     ` Greg Kroah-Hartman
2017-04-28  9:11       ` Michael Mera
2017-04-28  9:36         ` Greg Kroah-Hartman
2017-04-28 14:43           ` [PATCH v3] " Michael Mera
2017-04-28 15:52             ` Greg Kroah-Hartman [this message]
2017-04-29  1:24               ` Michael Mera
2017-05-09 23:48                 ` [PATCH v4] staging: speakup: fix unnecessary long line Michael Mera

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=20170428155225.GA18808@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=chris@the-brannons.com \
    --cc=dev@michaelmera.com \
    --cc=kirk@reisers.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=w.d.hubbs@gmail.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.