linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Doug Smythies <dsmythies@telus.net>
To: Len Brown <lenb@kernel.org>
Cc: Linux PM list <linux-pm@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Doug Smythies <dsmythies@telus.net>
Subject: Re: [GIT PULL] turbostat for Linux-6.7 (with signed tag)
Date: Sun, 12 Nov 2023 07:51:08 -0800	[thread overview]
Message-ID: <CAAYoRsXvKwhrw3gRQJ-STO48_7yxEiqwt5tgzDbkzA--N_XX6A@mail.gmail.com> (raw)
In-Reply-To: <CAJvTdK=OSTgYkut=-r95nAYOvVfUt3Cah92qudifeQW4ZJHT7Q@mail.gmail.com>

On Fri, Nov 10, 2023 at 7:39 PM Len Brown <lenb@kernel.org> wrote:
...
>
> (Same code as previous pull request, with addition of a signed tag.
>  Hopefully it verifies okay at your end.)
>
> Turbostat features are now table-driven (Rui Zhang)
> Add support for some new platforms (Sumeet Pawnikar, Rui Zhang)
> Gracefully run in configs when CPUs are limited (Rui Zhang, Srinivas Pandruvada)
> misc minor fixes.

Hi Len,
What about the patches that have been submitted since your last turbostat update
release of 2023.03.17? I submitted one on 2023.04.03. I haven't sent "RESEND"s,
because I know you only do update releases every 1/2 year or so, and in the past
you have always dealt with the interim patches then.

Reference:
https://patchwork.kernel.org/project/linux-pm/list/?series=&submitter=&state=&q=&archive=&delegate=107

... Doug

>
> thanks!
> Len Brown, Intel Open Source Technology Center
>
... [deleted]...

  parent reply	other threads:[~2023-11-12 15:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-08  5:03 [GIT PULL] turbostat for Linux-6.7 Len Brown
2023-11-10 17:19 ` Linus Torvalds
2023-11-11  3:39   ` [GIT PULL] turbostat for Linux-6.7 (with signed tag) Len Brown
2023-11-11 22:05     ` Linus Torvalds
2023-11-12 15:51     ` Doug Smythies [this message]
2023-11-13  3:21       ` Len Brown
2023-11-18 18:02 ` [GIT PULL] turbostat for Linux-6.7 pr-tracker-bot

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=CAAYoRsXvKwhrw3gRQJ-STO48_7yxEiqwt5tgzDbkzA--N_XX6A@mail.gmail.com \
    --to=dsmythies@telus.net \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@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).