From: Sudeep Holla <sudeep.holla@arm.com>
To: Conor.Dooley@microchip.com, gregkh@linuxfoundation.org
Cc: palmer@dabbelt.com, catalin.marinas@arm.com, will@kernel.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, atishp@atishpatra.org,
Brice.Goglin@inria.fr
Subject: Re: [GIT PULL] Fix RISC-V's arch-topology reporting
Date: Tue, 16 Aug 2022 10:12:43 +0100 [thread overview]
Message-ID: <20220816091243.apz7p2rb4wbxdh2t@bogus> (raw)
In-Reply-To: <4849490e-b362-c13a-c2e4-82acc3268a3f@microchip.com>
On Mon, Aug 15, 2022 at 10:14:55PM +0000, Conor.Dooley@microchip.com 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?
I don't have any other patch(other than a fix that I requested Greg to
pick it up directly yesterday) and since you have tagged it already, may be
Greg can pull this or patches directly based on his preference.
--
Regards,
Sudeep
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-08-16 9:14 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 [this message]
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
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=20220816091243.apz7p2rb4wbxdh2t@bogus \
--to=sudeep.holla@arm.com \
--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=will@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