From: "andriy.shevchenko@linux.intel.com" <andriy.shevchenko@linux.intel.com>
To: "Ruhl, Michael J" <michael.j.ruhl@intel.com>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
"david.e.box@linux.intel.com" <david.e.box@linux.intel.com>,
"ilpo.jarvinen@linux.intel.com" <ilpo.jarvinen@linux.intel.com>,
"Brost, Matthew" <matthew.brost@intel.com>,
"hdegoede@redhat.com" <hdegoede@redhat.com>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Subject: Re: [PATCH v10] drm/xe/vsec: Support BMG devices
Date: Mon, 12 Aug 2024 22:54:32 +0300 [thread overview]
Message-ID: <ZrpoeG2jMR3w37ps@smile.fi.intel.com> (raw)
In-Reply-To: <IA1PR11MB64186207DB7E251BF2C688A4C1852@IA1PR11MB6418.namprd11.prod.outlook.com>
On Mon, Aug 12, 2024 at 06:14:31PM +0000, Ruhl, Michael J wrote:
> Hmm,
>
> This is what the commit message looked like when I sent it:
>
> The Battlemage (BMG) discrete graphics card supports
> the Platform, > Monitoring Technology (PMT) feature
> directly on the primary PCI device.
>
> Utilize the PMT callback API to add support for the BMG
> devices.
>
> Not sure why it ended up here without the <cr>s?
Most likely MS Office happened in between and mangled the message.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-08-12 19:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 18:08 [PATCH v10] drm/xe/vsec: Support BMG devices Michael J. Ruhl
2024-08-12 18:14 ` ✗ CI.Patch_applied: failure for " Patchwork
2024-08-12 18:14 ` [PATCH v10] " Ruhl, Michael J
2024-08-12 19:54 ` andriy.shevchenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-12 20:01 Michael J. Ruhl
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=ZrpoeG2jMR3w37ps@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=david.e.box@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@intel.com \
--cc=michael.j.ruhl@intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rodrigo.vivi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox