mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
	Linux Documentation <linux-doc@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Power Management <linux-pm@vger.kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Amit Kucheria <amitk@kernel.org>, Zhang Rui <rui.zhang@intel.com>,
	Thorsten Leemhuis <linux@leemhuis.info>,
	Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
	Arjan van de Ven <arjan@linux.intel.com>,
	Jacob Pan <jacob.jun.pan@linux.intel.com>,
	oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 0/3] Documentation fixes for thermal/bleeding-edge
Date: Mon, 13 Feb 2023 02:18:23 -0800	[thread overview]
Message-ID: <f6fc39d2060c964d32b6610956b66e8d3151d926.camel@linux.intel.com> (raw)
In-Reply-To: <20230213100800.28333-1-bagasdotme@gmail.com>

On Mon, 2023-02-13 at 17:07 +0700, Bagas Sanjaya wrote:
> Here are documentation fixes for thermal/bleeding-edge tree. The
> first two patches are fixes to recently reported kernel test robot
> reports whereas the third patch is cosmetical (formatting).
> 
I am fine picking up this patchset over mine, as this series has  one
additional fix.

	[thermal-bleeding-edge][PATCH] thermal: intel: powerclamp: Fix
warnings

Thanks,
Srinivas


> Bagas Sanjaya (3):
>   Documentation: admin-guide: Add toctree entry for thermal docs
>   Documentation: powerclamp: Escape wildcard in cpumask description
>   Documentation: powerclamp: Fix numbered lists formatting
> 
>  Documentation/admin-guide/index.rst               |  2 +-
>  Documentation/admin-guide/thermal/index.rst       |  8 ++++++++
>  .../admin-guide/thermal/intel_powerclamp.rst      | 15 +++++++++----
> --
>  3 files changed, 18 insertions(+), 7 deletions(-)
>  create mode 100644 Documentation/admin-guide/thermal/index.rst
> 
> 
> base-commit: 1c7337f9eef60b8ce8a4b8c96d197e230d60b6b2


  parent reply	other threads:[~2023-02-13 10:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13 10:07 Bagas Sanjaya
2023-02-13 10:07 ` [PATCH 1/3] Documentation: admin-guide: Add toctree entry for thermal docs Bagas Sanjaya
2023-02-13 10:15   ` srinivas pandruvada
2023-02-14  2:16     ` Bagas Sanjaya
2023-02-13 10:08 ` [PATCH 2/3] Documentation: powerclamp: Escape wildcard in cpumask description Bagas Sanjaya
2023-02-13 10:17   ` srinivas pandruvada
2023-02-14  2:16     ` Bagas Sanjaya
2023-02-13 10:08 ` [PATCH 3/3] Documentation: powerclamp: Fix numbered lists formatting Bagas Sanjaya
2023-02-13 10:18 ` srinivas pandruvada [this message]
2023-02-13 15:34   ` [PATCH 0/3] Documentation fixes for thermal/bleeding-edge Rafael J. Wysocki

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=f6fc39d2060c964d32b6610956b66e8d3151d926.camel@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=amitk@kernel.org \
    --cc=arjan@linux.intel.com \
    --cc=bagasdotme@gmail.com \
    --cc=corbet@lwn.net \
    --cc=daniel.lezcano@linaro.org \
    --cc=jacob.jun.pan@linux.intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=mchehab+samsung@kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=rafael@kernel.org \
    --cc=rui.zhang@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

all inboxes | Powered by JetHome®