All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Nadim Almas <nadim.902@gmail.com>
Cc: devel@driverdev.osuosl.org, markh@compro.ne,
	linux-kernel@vger.kernel.org
Subject: Re: Fwd: [PATCH] Staging:dgnc:dgnc_neo: fixed 80 character line limit coding style issue
Date: Sun, 2 Oct 2016 19:49:04 +0200	[thread overview]
Message-ID: <20161002174904.GA22964@kroah.com> (raw)
In-Reply-To: <CANQNnfHSTJp6E0-4xN+pw4SZLyNiGokKeY+zRPVEDAfaW0afjw@mail.gmail.com>


A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

A: No.
Q: Should I include quotations after my reply?


http://daringfireball.net/2007/07/on_top

On Sun, Oct 02, 2016 at 10:11:12PM +0530, Nadim Almas wrote:
> So my first patch is correct?

I don't remember, I think someone else already did the same work as you,
but as I deal with hundreds of patches a day, I can't recall.  Resync on
my staging-testing branch of staging.git and rebase your patch and do
more cleanup than just one tiny one and then resend.

thanks,

greg k-h

      reply	other threads:[~2016-10-02 17:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-30 21:49 [PATCH] Staging:dgnc:dgnc_neo: fixed 80 character line limit coding style issue Nadim Almas
2016-10-02 15:23 ` Greg KH
     [not found]   ` <CANQNnfGy50kygxezO3WEt+zHh5EH5RRgvKkJA0OFU7BFPMn5KQ@mail.gmail.com>
     [not found]     ` <20161002153937.GA21118@kroah.com>
2016-10-02 15:43       ` Fwd: " Nadim Almas
2016-10-02 16:09         ` Greg KH
2016-10-02 16:41           ` Nadim Almas
2016-10-02 17:49             ` Greg KH [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=20161002174904.GA22964@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markh@compro.ne \
    --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.