All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Nadim Almas <nadim.902@gmail.com>
Cc: hvaibhav.linux@gmail.com, johan@kernel.org,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging:greybus:arche-apb-ctrl: fixed some coding style issue
Date: Wed, 12 Oct 2016 15:25:19 +0200	[thread overview]
Message-ID: <20161012132519.GA22556@kroah.com> (raw)
In-Reply-To: <20161011194954.GA9619@gmail.com>

On Tue, Oct 11, 2016 at 12:49:54PM -0700, Nadim Almas wrote:
> fixed trailing */ Block comments and 80 character line limit coding style issue
> 
> Signed-off-by: Nadim Almas <nadim.902@gmail.com>
> ---

Someone else already sent this same patch in before you, sorry :(

  reply	other threads:[~2016-10-12 13:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-11 19:49 [PATCH] Staging:greybus:arche-apb-ctrl: fixed some coding style issue Nadim Almas
2016-10-12 13:25 ` Greg KH [this message]
2016-10-12 14:03   ` Nadim Almas
2016-10-12 14:45     ` Greg KH
2016-10-13  4:00       ` Alexander Alemayhu
2016-10-13  7:08         ` Greg KH

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=20161012132519.GA22556@kroah.com \
    --to=greg@kroah.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=hvaibhav.linux@gmail.com \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nadim.902@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.