All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jinpu Wang <jinpu.wang@cloud.ionos.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	tony.luck@intel.com, Arjan van de Ven <arjan@linux.intel.com>,
	linux-kernel@vger.kernel.org,
	Elmar Gerdes <elmar.gerdes@cloud.ionos.com>
Subject: Re: Is 2nd Generation Intel(R) Xeon(R) Processors (Formerly Cascade Lake) affected by MDS
Date: Fri, 24 May 2019 13:45:47 +0200	[thread overview]
Message-ID: <20190524114547.GA686@kroah.com> (raw)
In-Reply-To: <CAMGffE=xsHWMNoGn75wzv9CLrQ81OizgLiwDEwqKw14i_eVj8Q@mail.gmail.com>

On Fri, May 24, 2019 at 11:23:40AM +0200, Jinpu Wang wrote:
> This e-mail may contain confidential and/or privileged information. If
> you are not the intended recipient of this e-mail, you are hereby
> notified that saving, distribution or use of the content of this
> e-mail in any way is prohibited. If you have received this e-mail in
> error, please notify the sender and delete the e-mail.

I am not allowed to respond to such emails as they do not mix well with
Linux kernel development requirements, sorry.

  reply	other threads:[~2019-05-24 11:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-24  9:23 Is 2nd Generation Intel(R) Xeon(R) Processors (Formerly Cascade Lake) affected by MDS Jinpu Wang
2019-05-24 11:45 ` Greg Kroah-Hartman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-05-24 13:19 Jinpu Wang
2019-05-24 14:17 ` Greg Kroah-Hartman
2019-05-24 14:45   ` Tony Luck
2019-05-24 15:14     ` Jinpu Wang
2019-05-24 15:19       ` Greg Kroah-Hartman

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=20190524114547.GA686@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arjan@linux.intel.com \
    --cc=elmar.gerdes@cloud.ionos.com \
    --cc=jinpu.wang@cloud.ionos.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.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.