From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: ALKML <linux-arm-kernel@lists.infradead.org>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] cacheinfo/arch_topology: Updates for v5.20
Date: Fri, 8 Jul 2022 15:36:16 +0200 [thread overview]
Message-ID: <Ysgy0Fdww3dIe2zL@kroah.com> (raw)
In-Reply-To: <20220706124644.2276077-1-sudeep.holla@arm.com>
On Wed, Jul 06, 2022 at 01:46:44PM +0100, Sudeep Holla wrote:
> Hi Greg,
>
> This is my first pull request to you, not sure if you are open to
> pull request or prefer pulling the patch series directly. I am fine
> either way. You can ignore this and pull the patches from[1] if you
> prefer.
>
> Most of these changes are in -next for almost 2 weeks with small update
> to fix issue reported on RISC-V last week. The small changes in ACPI
> and arm64 are acked-by Rafael and Catalin.
This worked great, thanks!
greg k-h
prev parent reply other threads:[~2022-07-08 13:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 12:46 [GIT PULL] cacheinfo/arch_topology: Updates for v5.20 Sudeep Holla
2022-07-08 13:36 ` Greg Kroah-Hartman [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=Ysgy0Fdww3dIe2zL@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--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