From: Will Deacon <will@kernel.org>
To: Conor.Dooley@microchip.com
Cc: sudeep.holla@arm.com, palmer@dabbelt.com,
catalin.marinas@arm.com, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, atishp@atishpatra.org,
Brice.Goglin@inria.fr, gregkh@linuxfoundation.org
Subject: Re: [GIT PULL] Fix RISC-V's arch-topology reporting
Date: Wed, 7 Sep 2022 17:41:41 +0100 [thread overview]
Message-ID: <20220907164140.GA30683@willie-the-truck> (raw)
In-Reply-To: <afa3b7a8-3615-36bb-4850-b7966028f74c@microchip.com>
On Wed, Sep 07, 2022 at 04:39:31PM +0000, Conor.Dooley@microchip.com wrote:
> On 15/08/2022 23:14, Conor Dooley wrote:
> > Hey Will/Palmer/Sudeep,
> >
> > Catalin suggested [0] dropping the CC: stable for the arm64 patch and
> > instead making it a specific prereq of the RISC-V patch & making a PR,
> > so here we are.. I was still up when -rc1 came out so pushed it last
> > night to get the test coverage, but LKP seems to not have reported a
> > build success since early on the 13th so not holding my horses! I built
> > it again for both ARMs and RISC-V myself.
> >
> > I tagged it tonight, so it's on conor/linux.git as riscv-topo-on-6.0-rc1
> > with the prereq specified.
> >
> > Not sure if you want to merge this too Sudeep or if that's up to Greg?
>
> What's the story with this from an arm64 & topology PoV?
> Palmer merged this into riscv/for-next a couple weeks ago, so just
> wondering what the craic is on the other fronts.
If it's merged in the riscv tree, then I guess we don't need to do anything
on the arm64 side. It would be handy if it's on its own branch, however,
just in case we run into a conflict later on during the cycle.
Catalin -- this is the series we spoke about the other day touching the
topology code.
Cheers,
Will
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2022-09-07 16:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 22:14 [GIT PULL] Fix RISC-V's arch-topology reporting Conor.Dooley
2022-08-16 9:12 ` Sudeep Holla
2022-08-18 21:03 ` Palmer Dabbelt
2022-08-18 21:10 ` Conor.Dooley
2022-08-18 21:15 ` Palmer Dabbelt
2022-09-07 16:39 ` Conor.Dooley
2022-09-07 16:41 ` Will Deacon [this message]
2022-09-07 16:44 ` 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=20220907164140.GA30683@willie-the-truck \
--to=will@kernel.org \
--cc=Brice.Goglin@inria.fr \
--cc=Conor.Dooley@microchip.com \
--cc=atishp@atishpatra.org \
--cc=catalin.marinas@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=sudeep.holla@arm.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;
as well as URLs for NNTP newsgroup(s).