All of lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <mail@conchuod.ie>
To: zong.li@sifive.com, robh+dt@kernel.org, palmer@dabbelt.com,
	daire.mcnamara@microchip.com, niklas.cassel@wdc.com,
	hahnjo@hahnjo.de, kernel@esmil.dk, aou@eecs.berkeley.edu,
	geert@linux-m68k.org, paul.walmsley@sifive.com, mail@conchuod.ie,
	damien.lemoal@opensource.wdc.com,
	krzysztof.kozlowski+dt@linaro.org
Cc: Conor Dooley <conor.dooley@microchip.com>,
	devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org, Brice.Goglin@inria.fr
Subject: Re: (subset) [PATCH 0/5] RISC-V: Add cpu-map topology information nodes
Date: Thu,  7 Jul 2022 23:29:04 +0100	[thread overview]
Message-ID: <165723282709.4170238.17783892176422654947.b4-ty@microchip.com> (raw)
In-Reply-To: <20220705190435.1790466-1-mail@conchuod.ie>

From: Conor Dooley <conor.dooley@microchip.com>

On Tue, 5 Jul 2022 20:04:31 +0100, Conor Dooley wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
> 
> It was reported to me that the Hive Unmatched incorrectly reports
> its topology to hwloc, but the StarFive VisionFive did in [0] &
> a subsequent off-list email from Brice (the hwloc maintainer).
> This turned out not to be entirely true, the /downstream/ version
> of the VisionFive does work correctly but not upstream, as the
> downstream devicetree has a cpu-map node that was added recently.
> 
> [...]

Applied to dt-for-next, thanks!

[4/5] riscv: dts: microchip: Add mpfs' topology information
      https://git.kernel.org/conor/c/88d319c6abae

The rest is yours Palmer once reviewed :)

Thanks,
Conor.

WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <mail@conchuod.ie>
To: zong.li@sifive.com, robh+dt@kernel.org, palmer@dabbelt.com,
	daire.mcnamara@microchip.com, niklas.cassel@wdc.com,
	hahnjo@hahnjo.de, kernel@esmil.dk, aou@eecs.berkeley.edu,
	geert@linux-m68k.org, paul.walmsley@sifive.com, mail@conchuod.ie,
	damien.lemoal@opensource.wdc.com,
	krzysztof.kozlowski+dt@linaro.org
Cc: Conor Dooley <conor.dooley@microchip.com>,
	devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org, Brice.Goglin@inria.fr
Subject: Re: (subset) [PATCH 0/5] RISC-V: Add cpu-map topology information nodes
Date: Thu,  7 Jul 2022 23:29:04 +0100	[thread overview]
Message-ID: <165723282709.4170238.17783892176422654947.b4-ty@microchip.com> (raw)
In-Reply-To: <20220705190435.1790466-1-mail@conchuod.ie>

From: Conor Dooley <conor.dooley@microchip.com>

On Tue, 5 Jul 2022 20:04:31 +0100, Conor Dooley wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
> 
> It was reported to me that the Hive Unmatched incorrectly reports
> its topology to hwloc, but the StarFive VisionFive did in [0] &
> a subsequent off-list email from Brice (the hwloc maintainer).
> This turned out not to be entirely true, the /downstream/ version
> of the VisionFive does work correctly but not upstream, as the
> downstream devicetree has a cpu-map node that was added recently.
> 
> [...]

Applied to dt-for-next, thanks!

[4/5] riscv: dts: microchip: Add mpfs' topology information
      https://git.kernel.org/conor/c/88d319c6abae

The rest is yours Palmer once reviewed :)

Thanks,
Conor.

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

  parent reply	other threads:[~2022-07-07 22:29 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-05 19:04 [PATCH 0/5] RISC-V: Add cpu-map topology information nodes Conor Dooley
2022-07-05 19:04 ` Conor Dooley
2022-07-05 19:04 ` [PATCH 1/5] riscv: dts: starfive: Add JH7100 CPU topology Conor Dooley
2022-07-05 19:04   ` Conor Dooley
2022-07-05 19:04 ` [PATCH 2/5] riscv: dts: sifive: Add fu540 topology information Conor Dooley
2022-07-05 19:04   ` Conor Dooley
2022-07-05 19:04 ` [PATCH 3/5] riscv: dts: sifive: Add fu740 " Conor Dooley
2022-07-05 19:04   ` Conor Dooley
2022-07-05 19:04 ` [PATCH 4/5] riscv: dts: microchip: Add mpfs' " Conor Dooley
2022-07-05 19:04   ` Conor Dooley
2022-07-14 22:04   ` Palmer Dabbelt
2022-07-14 22:04     ` Palmer Dabbelt
2022-07-05 19:04 ` [PATCH 5/5] riscv: dts: canaan: Add k210 " Conor Dooley
2022-07-05 19:04   ` Conor Dooley
2022-07-06  3:49   ` Damien Le Moal
2022-07-06  3:49     ` Damien Le Moal
2022-07-05 20:19 ` [PATCH 0/5] RISC-V: Add cpu-map topology information nodes Sudeep Holla
2022-07-05 20:19   ` Sudeep Holla
2022-07-05 20:33   ` Conor.Dooley
2022-07-05 20:33     ` Conor.Dooley
2022-07-05 23:03     ` Conor.Dooley
2022-07-05 23:03       ` Conor.Dooley
2022-07-06  9:21       ` Sudeep Holla
2022-07-06  9:21         ` Sudeep Holla
2022-07-06  9:43         ` Conor.Dooley
2022-07-06  9:43           ` Conor.Dooley
2022-07-06 10:03           ` Sudeep Holla
2022-07-06 10:03             ` Sudeep Holla
2022-07-06 10:11             ` Conor.Dooley
2022-07-06 10:11               ` Conor.Dooley
2022-07-06 13:04         ` Conor.Dooley
2022-07-06 13:04           ` Conor.Dooley
2022-07-06 14:00           ` Sudeep Holla
2022-07-06 14:00             ` Sudeep Holla
2022-07-06  9:18     ` Sudeep Holla
2022-07-06  9:18       ` Sudeep Holla
2022-07-07 22:29 ` Conor Dooley [this message]
2022-07-07 22:29   ` (subset) " Conor Dooley

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=165723282709.4170238.17783892176422654947.b4-ty@microchip.com \
    --to=mail@conchuod.ie \
    --cc=Brice.Goglin@inria.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor.dooley@microchip.com \
    --cc=daire.mcnamara@microchip.com \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=hahnjo@hahnjo.de \
    --cc=kernel@esmil.dk \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=niklas.cassel@wdc.com \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh+dt@kernel.org \
    --cc=zong.li@sifive.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.