public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Palmer Dabbelt <palmer@rivosinc.com>, suagrfillet@gmail.com
Cc: alexs@kernel.org, siyanteng@loongson.cn, robh@kernel.org,
	Conor Dooley <conor.dooley@microchip.com>,
	leyfoon.tan@starfivetech.com, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
	suagrfillet@gmail.com
Subject: Re: [PATCH] sched/doc: supplement CPU capacity with RISC-V
Date: Tue, 07 Mar 2023 10:18:55 -0700	[thread overview]
Message-ID: <87y1o8o4xs.fsf@meer.lwn.net> (raw)
In-Reply-To: <87wn41wi9b.fsf@meer.lwn.net>

Jonathan Corbet <corbet@lwn.net> writes:

> Palmer Dabbelt <palmer@rivosinc.com> writes:
>
>> Happy to take this through the RISC-V tree, but I'll hold off for a bit 
>> and let the doc folks have a chance to chime in (or just pick it up).  
>> I'm planning on sending something later this week either way.
>
> "Doc folks" are fine if you just include this one in the pull you're
> doing.

So it looks like that didn't happen...so I'll go ahead and apply this to
my fixes branch.

Thanks,

jon

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

      reply	other threads:[~2023-03-07 17:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-27 10:59 [PATCH] sched/doc: supplement CPU capacity with RISC-V Song Shuai
2023-02-27 11:56 ` Conor Dooley
2023-02-27 12:40   ` Song Shuai
2023-02-27 12:55     ` Conor Dooley
2023-02-28  2:00       ` Leyfoon Tan
2023-02-28  7:11 ` Alex Shi
2023-02-28 21:59 ` Palmer Dabbelt
2023-02-28 22:13   ` Jonathan Corbet
2023-03-07 17:18     ` Jonathan Corbet [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=87y1o8o4xs.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=alexs@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=leyfoon.tan@starfivetech.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@rivosinc.com \
    --cc=robh@kernel.org \
    --cc=siyanteng@loongson.cn \
    --cc=suagrfillet@gmail.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