platform-driver-x86.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David E. Box" <david.e.box@linux.intel.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: hdegoede@redhat.com, mgross@linux.intel.com, bhelgaas@google.com,
	alexey.budankov@linux.intel.com, linux-kernel@vger.kernel.org,
	platform-driver-x86@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH V9 0/5] Intel Platform Monitoring Technology
Date: Thu, 29 Oct 2020 09:09:03 -0700	[thread overview]
Message-ID: <a5f95b717ce4a767d10689d54bc166ea534fd98a.camel@linux.intel.com> (raw)
In-Reply-To: <20201029151633.GB4127@dell>

Hi Lee,

On Thu, 2020-10-29 at 15:16 +0000, Lee Jones wrote:

...

> > Changes from V8:
> >  	- Rebase on 5.10-rc1
> > 	- Add missing changes in MFD patch from V7 that were
> > accidentally
> > 	  dropped in V8
> 
> Which changes are those?
> 
> Do I need to re-review?

Should have mentioned here. Patch 2 is the only one that changed. It
was corrected to be the last patch you reviewed (which was accidentally
reverted in V8) plus I dropped this dev_err:

       if (!found_devices) {
               dev_err(&pdev->dev, "No supported PMT capabilities
found.\n");
               return -ENODEV;
       }

There are no more changes planned for this series and we're still
looking to merge in 5.11. Thanks.

David


  reply	other threads:[~2020-10-29 16:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29  1:44 [PATCH V9 0/5] Intel Platform Monitoring Technology David E. Box
2020-10-29  1:44 ` [PATCH V9 1/5] PCI: Add defines for Designated Vendor-Specific Extended Capability David E. Box
2020-10-29 15:16 ` [PATCH V9 0/5] Intel Platform Monitoring Technology Lee Jones
2020-10-29 16:09   ` David E. Box [this message]
2020-11-04 11:17 ` [GIT PULL] Immutable branch between MFD and x86 due for the v5.11 merge window Lee Jones
2020-11-09 10:39   ` Hans de Goede

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=a5f95b717ce4a767d10689d54bc166ea534fd98a.camel@linux.intel.com \
    --to=david.e.box@linux.intel.com \
    --cc=alexey.budankov@linux.intel.com \
    --cc=bhelgaas@google.com \
    --cc=hdegoede@redhat.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mgross@linux.intel.com \
    --cc=platform-driver-x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).