public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@infradead.org>
To: "Chakravarty, Souvik K" <souvik.k.chakravarty@intel.com>
Cc: "Bhardwaj, Rajneesh" <rajneesh.bhardwaj@intel.com>,
	"platform-driver-x86@vger.kernel.org" 
	<platform-driver-x86@vger.kernel.org>,
	"andy@infradead.org" <andy@infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Murthy, Shanth" <shanth.murthy@intel.com>
Subject: Re: [PATCH 1/3] platform/x86: Add GLK PSS Event Table
Date: Thu, 20 Jul 2017 14:06:27 -0700	[thread overview]
Message-ID: <20170720210627.GC16076@fury> (raw)
In-Reply-To: <5F7315E704FA0841B5DFCE90329B2BB462E9006C@BGSMSX102.gar.corp.intel.com>

On Mon, Jul 17, 2017 at 05:18:54AM +0000, Chakravarty, Souvik K wrote:
> +1 From me.

Souvik, as the listed maintainer for this driver, what I require from
you is a complete Acked-by or a Reviewed-by line, preferably the latter,
and preferably after an actual review with comments. +1 has no semantic
meaning in the Linux kernel development process, and one line approvals,
especially from the same company, have little incremental value.

For details, please see:
Documentation/process/5.Posting.rst
Documentation/submitting-patches.rst

Thanks,

-- 
Darren Hart
VMware Open Source Technology Center

  reply	other threads:[~2017-07-20 21:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-14 11:53 [PATCH 1/3] platform/x86: Add GLK PSS Event Table Rajneesh Bhardwaj
2017-07-14 11:53 ` [PATCH 2/3] Telemetry: remove redundant macro definition Rajneesh Bhardwaj
2017-07-14 11:53 ` [PATCH 3/3] platform/x86: Add Audio domain PG status events Rajneesh Bhardwaj
2017-07-17  5:18   ` Chakravarty, Souvik K
2017-07-19 13:38     ` Rajneesh Bhardwaj
2017-07-20  4:06       ` Chakravarty, Souvik K
2017-07-17  5:18 ` [PATCH 1/3] platform/x86: Add GLK PSS Event Table Chakravarty, Souvik K
2017-07-20 21:06   ` Darren Hart [this message]
2017-07-21  3:21     ` Chakravarty, Souvik K

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=20170720210627.GC16076@fury \
    --to=dvhart@infradead.org \
    --cc=andy@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=rajneesh.bhardwaj@intel.com \
    --cc=shanth.murthy@intel.com \
    --cc=souvik.k.chakravarty@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