From: <Mario.Limonciello@dell.com>
To: <gayatri.kammela@intel.com>, <andy.shevchenko@gmail.com>
Cc: <platform-driver-x86@vger.kernel.org>,
<vishwanath.somayaji@intel.com>, <dvhart@infradead.org>,
<linux-kernel@vger.kernel.org>, <charles.d.prestopine@intel.com>,
<peterz@infradead.org>, <srinivas.pandruvada@intel.com>,
<andriy.shevchenko@linux.intel.com>, <kan.liang@intel.com>,
<david.e.box@intel.com>, <rajneesh.bhardwaj@intel.com>,
<tony.luck@intel.com>
Subject: RE: [PATCH v3 0/7] x86/intel_pmc_core: Add Tiger Lake, Elkhart Lake
Date: Mon, 18 Nov 2019 18:18:51 +0000 [thread overview]
Message-ID: <9b880cb6585d4608814598517fe5d675@AUSX13MPC105.AMER.DELL.COM> (raw)
In-Reply-To: <MN2PR11MB3711EDFC967C295689E109DEF24D0@MN2PR11MB3711.namprd11.prod.outlook.com>
> -----Original Message-----
> From: platform-driver-x86-owner@vger.kernel.org <platform-driver-x86-
> owner@vger.kernel.org> On Behalf Of Kammela, Gayatri
> Sent: Monday, November 18, 2019 12:11 PM
> To: Andy Shevchenko
> Cc: Platform Driver; Somayaji, Vishwanath; Darren Hart; Linux Kernel Mailing
> List; Prestopine, Charles D; Peter Zijlstra; Pandruvada, Srinivas; Andy
> Shevchenko; Liang, Kan; Box, David E; Bhardwaj, Rajneesh; Luck, Tony
> Subject: RE: [PATCH v3 0/7] x86/intel_pmc_core: Add Tiger Lake, Elkhart Lake
>
>
> [EXTERNAL EMAIL]
>
> > > All the information regarding the PCH IPs and names of IPs will be
> > > available in Intel's Platform Controller Hub (PCH) External Design
> > > Specification (EDS) document expected to be released in 2020 before
> > > product launch.
> >
> > Thanks, though you forgot to fix all prefixes in the mails. We have
> > platform/x86: $DRIVER_NAME: ...
> >
> Hi Andy! Sorry I think I misunderstood your comment last time. Just to make
> sure, the prefix should the pattern in this case
> "platform/x86: intel_pmc_core: " and should be same for all the patches in the
> series right?
>
> > Also consider Mario's comment (I didn't hear back from you on it).
> Sorry about that. I am planning on sending it a single patch excluding it from the
> series since we received a request from Dell. Please let me know if you think this
> patch should be included in the series.
Just to make it clear to those on the list - the request from Dell was off list and separately
from my comment in adjusting the ordering. A convenient side effect is that it will
take into consideration my comment too :)
next prev parent reply other threads:[~2019-11-18 18:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 17:01 [PATCH v3 0/7] x86/intel_pmc_core: Add Tiger Lake, Elkhart Lake Gayatri Kammela
2019-11-14 17:01 ` [PATCH v3 1/7] x86/intel_pmc_core: Fix the SoC naming inconsistency Gayatri Kammela
2019-11-14 17:01 ` [PATCH v3 2/7] x86/intel_pmc_core: Clean up: Remove comma after the termination line Gayatri Kammela
2019-11-14 17:01 ` [PATCH v3 3/7] x86/intel_pmc_core: Create platform dependent pmc bitmap structs Gayatri Kammela
2019-11-14 17:01 ` [PATCH v3 4/7] x86/intel_pmc_core: Make debugfs entry for pch_ip_power_gating_status conditional Gayatri Kammela
2019-11-14 17:01 ` [PATCH v3 5/7] platform/x86: Add Tiger Lake (TGL) platform support to intel_pmc_core driver Gayatri Kammela
2019-11-14 17:01 ` [PATCH v3 6/7] platform/x86: Add Atom based Elkhart Lake (EHL) " Gayatri Kammela
2019-11-14 17:01 ` [PATCH v3 7/7] platform/x86: Add Comet Lake (CML) " Gayatri Kammela
2019-11-14 18:50 ` Mario.Limonciello
2019-11-18 18:06 ` Kammela, Gayatri
2019-11-18 10:50 ` [PATCH v3 0/7] x86/intel_pmc_core: Add Tiger Lake, Elkhart Lake Andy Shevchenko
2019-11-18 18:11 ` Kammela, Gayatri
2019-11-18 18:18 ` Mario.Limonciello [this message]
2019-11-18 19:12 ` Kammela, Gayatri
2019-11-18 18:23 ` Andy Shevchenko
2019-11-18 19:15 ` Kammela, Gayatri
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=9b880cb6585d4608814598517fe5d675@AUSX13MPC105.AMER.DELL.COM \
--to=mario.limonciello@dell.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=charles.d.prestopine@intel.com \
--cc=david.e.box@intel.com \
--cc=dvhart@infradead.org \
--cc=gayatri.kammela@intel.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rajneesh.bhardwaj@intel.com \
--cc=srinivas.pandruvada@intel.com \
--cc=tony.luck@intel.com \
--cc=vishwanath.somayaji@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;
as well as URLs for NNTP newsgroup(s).