All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jon Ringle <jringle@gridpoint.com>
Cc: "Ringle, Jonathan" <Jonathan.Ringle@gridpoint.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Add option to build with -O3
Date: Tue, 4 Mar 2014 22:31:11 -0800	[thread overview]
Message-ID: <20140305063111.GA8816@kroah.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1403050111490.24331@jringle-ubuntu>

On Wed, Mar 05, 2014 at 01:19:17AM -0500, Jon Ringle wrote:
> 
> 
> On Wed, 5 Mar 2014, Greg KH wrote:
> 
> > On Wed, Mar 05, 2014 at 12:37:56AM -0500, Jon Ringle wrote:
> > > The information contained in this transmission may contain confidential information.  If the reader of this message is not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited.  If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
> >
> > Because of this footer, I must destroy this message, kernel development
> > is not confidental.
> >
> 
> Obviously, this is a footer that is not added by me, but rather the mail
> server I am sending this message through. Besides, the footer indates it
> "may contain confidential information". The key word being *may*. Of
> course kernel development is never confidential and the content of any
> transmission done to the lkml is of public record. You and anyone who
> cares to read/comment this message on lkml is indeed the inteded
> recipient, therefore there is no need to destroy this message :)

But how do I know for sure that there isn't anything confidential in it?

> I sure hope your response was just in jest :)

Sadly, no, I have been advised that I am not supposed to respond to
messages with footers like that, and I am not allowed to take patches
with them either.

Now, I'm ignoring the first part (responding) to help you learn why your
patches will proabably always be ignored, please work to remove that
from your email server.

good luck,

greg k-h

  reply	other threads:[~2014-03-05  6:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-05  0:01 [PATCH] Add option to build with -O3 Jon Ringle
2014-03-05  5:09 ` Greg KH
2014-03-05  5:37   ` Jon Ringle
2014-03-05  6:08     ` Greg KH
2014-03-05  6:19       ` Jon Ringle
2014-03-05  6:31         ` Greg KH [this message]
2014-03-05 18:14         ` Valdis.Kletnieks
2014-03-06 13:28     ` Richard Weinberger
2014-03-07 12:39       ` Austin S Hemmelgarn
2014-03-07 12:42         ` Richard Weinberger
2014-03-07 12:51           ` Austin S Hemmelgarn
2014-03-07 13:48             ` Borislav Petkov
2014-03-05  7:32   ` Jon Ringle
2014-03-06  4:43     ` Greg KH
2014-03-05  7:36 jon
2014-03-06 12:28 ` Austin S Hemmelgarn

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=20140305063111.GA8816@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Jonathan.Ringle@gridpoint.com \
    --cc=jringle@gridpoint.com \
    --cc=linux-kernel@vger.kernel.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.