public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Kammela, Gayatri" <gayatri.kammela@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: markgross@kernel.org, david.e.box@linux.intel.com,
	srinivas.pandruvada@intel.com,
	platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/4] Add Raptor Lake and PCI error recovery support
Date: Tue, 5 Jul 2022 12:47:31 -0700	[thread overview]
Message-ID: <b617a83b-cde1-ed7f-cd5f-9eabcffffafb@linux.intel.com> (raw)
In-Reply-To: <ac7bfd35-203b-5002-a3ff-787ca1738a41@redhat.com>

On 7/2/2022 2:54 AM, Hans de Goede wrote:

> Hi,
>
> On 6/30/22 00:13, Gayatri Kammela wrote:
>> Hi,
>>
>> This patch set adds Raptor Lake support as well as PCI error recovery
>> support to PMT driver. It also has a rework patch and a fix for fixed
>> region handling.
>>
>> Patch 1: Rework early hardware code
>> Patch 2: Add support for Raptor Lake
>> Patch 3: Fix fixed region handling
>> Patch 4: Add PCI error recovery support to Intel PMT
> Thank you for your patch-series, I've applied the series to my
> review-hans branch:
> https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/log/?h=review-hans
>
> Note it will show up in my review-hans branch once I've pushed my
> local branch there, which might take a while.
>
> Once I've run some tests on this branch the patches there will be
> added to the platform-drivers-x86/for-next branch and eventually
> will be included in the pdx86 pull-request to Linus for the next
> merge-window.
>
> Regards,
>
> Hans
>
Thank you Hans!
>> David E. Box (3):
>>    platform/x86/intel/vsec: Rework early hardware code
>>    platform/x86/intel/vsec: Add support for Raptor Lake
>>    platform/x86/intel/pmt: telemetry: Fix fixed region handling
>>
>> Gayatri Kammela (1):
>>    platform/x86/intel/vsec: Add PCI error recovery support to Intel PMT
>>
>>   drivers/platform/x86/intel/pmt/class.c     |  23 ++--
>>   drivers/platform/x86/intel/pmt/telemetry.c |  18 ++-
>>   drivers/platform/x86/intel/vsec.c          | 130 ++++++++++++++++-----
>>   drivers/platform/x86/intel/vsec.h          |  11 +-
>>   4 files changed, 136 insertions(+), 46 deletions(-)
>>
>>
>> base-commit: 03c765b0e3b4cb5063276b086c76f7a612856a9a

      reply	other threads:[~2022-07-05 19:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-29 22:13 [PATCH v1 0/4] Add Raptor Lake and PCI error recovery support Gayatri Kammela
2022-06-29 22:13 ` [PATCH v1 1/4] platform/x86/intel/vsec: Rework early hardware code Gayatri Kammela
2022-06-29 22:13 ` [PATCH v1 2/4] platform/x86/intel/vsec: Add support for Raptor Lake Gayatri Kammela
2022-06-29 22:13 ` [PATCH v1 3/4] platform/x86/intel/pmt: telemetry: Fix fixed region handling Gayatri Kammela
2022-06-29 22:13 ` [PATCH v1 4/4] platform/x86/intel/vsec: Add PCI error recovery support to Intel PMT Gayatri Kammela
2022-07-02  9:54 ` [PATCH v1 0/4] Add Raptor Lake and PCI error recovery support Hans de Goede
2022-07-05 19:47   ` Kammela, Gayatri [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=b617a83b-cde1-ed7f-cd5f-9eabcffffafb@linux.intel.com \
    --to=gayatri.kammela@linux.intel.com \
    --cc=david.e.box@linux.intel.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markgross@kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=srinivas.pandruvada@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