public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: hdegoede@redhat.com, markgross@kernel.org,
	ilpo.jarvinen@linux.intel.com,
	platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] doc: TPMI: Add debugfs documentation
Date: Wed, 12 Jul 2023 16:07:19 -0700	[thread overview]
Message-ID: <39172b7b3016a7f850cbffe752cb8ccdb986623d.camel@linux.intel.com> (raw)
In-Reply-To: <ZK7DYuyo88efUje+@smile.fi.intel.com>

On Wed, 2023-07-12 at 18:14 +0300, Andy Shevchenko wrote:
> On Tue, Jul 11, 2023 at 03:09:49PM -0700, Srinivas Pandruvada wrote:
> > Describe fields in the TPMI debugfs folder.
> 
> ...
> 
> > +What:          /sys/kernel/debug/tpmi-<n>/pfs_dump
> > +Date:          December 2023
> 
> November ?
> 
Changed.


Thanks,
Srinivas

> > +KernelVersion: 6.6
> 
> ...
> 
> > +Date:          December 2023
> 
> > +Date:          December 2023
> 


      reply	other threads:[~2023-07-12 23:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-11 22:09 [PATCH v2 0/3] TPMI control and debugfs support Srinivas Pandruvada
2023-07-11 22:09 ` [PATCH v2 1/3] platform/x86/intel/tpmi: Read feature control status Srinivas Pandruvada
2023-07-12 15:05   ` Andy Shevchenko
2023-07-12 23:03     ` srinivas pandruvada
2023-07-11 22:09 ` [PATCH v2 2/3] platform/x86/intel/tpmi: Add debugfs interface Srinivas Pandruvada
2023-07-12 15:13   ` Andy Shevchenko
2023-07-12 23:06     ` srinivas pandruvada
2023-07-13 16:42       ` Andy Shevchenko
2023-07-11 22:09 ` [PATCH v2 3/3] doc: TPMI: Add debugfs documentation Srinivas Pandruvada
2023-07-12 15:14   ` Andy Shevchenko
2023-07-12 23:07     ` srinivas pandruvada [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=39172b7b3016a7f850cbffe752cb8ccdb986623d.camel@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=hdegoede@redhat.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markgross@kernel.org \
    --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