All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Chris Metcalf <cmetcalf@mellanox.com>
Cc: dwoods@mellanox.com, jh80.chung@samsung.com,
	ulf.hansson@linaro.org, stable@vger.kernel.org
Subject: Re: WTF: patch "[PATCH] mmc: dw_mmc: Use device_property_read instead of" was seriously submitted to be applied to the 4.12-stable tree?
Date: Fri, 28 Jul 2017 16:30:07 -0700	[thread overview]
Message-ID: <20170728233007.GA30604@kroah.com> (raw)
In-Reply-To: <f7af0a2e-6351-2725-3c7e-be6fc7adf28e@mellanox.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 Fri, Jul 28, 2017 at 09:52:57AM -0400, Chris Metcalf wrote:
> Ping?  Greg, I see that you released 4.12.4/4.9.40 without these patches,
> but
> not having heard back from you, I wondered if my reply below was lost and we
> were both waiting on each other.  Thanks!

No, it just went to the bottom of more important patches (i.e.
bugfixes.)  I'll reconsider this at a later point in time when I get a
chance...

thanks,

greg k-h

  reply	other threads:[~2017-07-28 23:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-24 23:32 WTF: patch "[PATCH] mmc: dw_mmc: Use device_property_read instead of" was seriously submitted to be applied to the 4.12-stable tree? gregkh
2017-07-25  1:22 ` Chris Metcalf
2017-07-25 14:48   ` Greg KH
2017-07-25 15:55     ` Chris Metcalf
2017-07-28 13:52       ` Chris Metcalf
2017-07-28 23:30         ` Greg KH [this message]
2017-07-29  2:02           ` Chris Metcalf
2017-08-07 19:51             ` Greg KH
2017-08-07 21:01               ` Greg KH
2017-08-08 14:29                 ` Chris Metcalf
2017-08-08 14:51                   ` 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=20170728233007.GA30604@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=cmetcalf@mellanox.com \
    --cc=dwoods@mellanox.com \
    --cc=jh80.chung@samsung.com \
    --cc=stable@vger.kernel.org \
    --cc=ulf.hansson@linaro.org \
    /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.