From: Andrew Morton <akpm@linux-foundation.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Reinette Chatre <reinette.chatre@intel.com>,
Tony Luck <tony.luck@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Fenghua Yu <fenghua.yu@intel.com>,
Maciej Wieczor-Retman <maciej.wieczor-retman@intel.com>,
Peter Newman <peternewman@google.com>,
James Morse <james.morse@arm.com>,
Babu Moger <babu.moger@amd.com>,
Drew Fustini <dfustini@baylibre.com>,
Dave Martin <Dave.Martin@arm.com>,
linux-kernel@vger.kernel.org, patches@lists.linux.dev
Subject: Re: [PATCH 0/3] Add and use get_cpu_cacheinfo_level()
Date: Tue, 4 Jun 2024 19:22:50 -0700 [thread overview]
Message-ID: <20240604192250.38295ab7ac9c8b01a434153e@linux-foundation.org> (raw)
In-Reply-To: <20240603170106.GHZl320tVKXp2HyUfb@fat_crate.local>
On Mon, 3 Jun 2024 19:01:06 +0200 Borislav Petkov <bp@alien8.de> wrote:
> > Could you please provide your guidance on how to achieve a smooth
> > upstream of this work?
>
> I'd prefer if resctrl patches go only through tip so that there's no
> unnecessary headaches with merging and coordination.
No probs. If/when patches turn up in a different tree (or get
convincingly nacked) I'll drop the mm.git copy.
I'll drop these now as things appear to be in hand.
next prev parent reply other threads:[~2024-06-05 2:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 19:57 [PATCH 0/3] Add and use get_cpu_cacheinfo_level() Tony Luck
2024-05-31 19:57 ` [PATCH 1/3] cacheinfo: Add function to get cacheinfo for a given (cpu, cachelevel) Tony Luck
2024-06-03 18:06 ` Reinette Chatre
2024-05-31 19:57 ` [PATCH 2/3] x86/resctrl: Replace open code cacheinfo search in pseudo_lock_region_init() Tony Luck
2024-06-03 18:07 ` Reinette Chatre
2024-05-31 19:57 ` [PATCH 3/3] x86/resctrl: Replace open code cacheinfo search in rdtgroup_cbm_to_size() Tony Luck
2024-06-03 18:07 ` Reinette Chatre
2024-06-04 18:03 ` Luck, Tony
2024-06-03 16:55 ` [PATCH 0/3] Add and use get_cpu_cacheinfo_level() Reinette Chatre
2024-06-03 17:01 ` Borislav Petkov
2024-06-03 17:18 ` Luck, Tony
2024-06-03 18:24 ` Borislav Petkov
2024-06-05 2:22 ` Andrew Morton [this message]
2024-06-05 8:14 ` Borislav Petkov
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=20240604192250.38295ab7ac9c8b01a434153e@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Dave.Martin@arm.com \
--cc=babu.moger@amd.com \
--cc=bp@alien8.de \
--cc=dfustini@baylibre.com \
--cc=fenghua.yu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=james.morse@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.wieczor-retman@intel.com \
--cc=patches@lists.linux.dev \
--cc=peternewman@google.com \
--cc=reinette.chatre@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.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