[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240605081421.GBZmAeXaQMH35dBRHt@fat_crate.local>
Date: Wed, 5 Jun 2024 10:14:21 +0200
From: Borislav Petkov <bp@...en8.de>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Reinette Chatre <reinette.chatre@...el.com>,
Tony Luck <tony.luck@...el.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
Fenghua Yu <fenghua.yu@...el.com>,
Maciej Wieczor-Retman <maciej.wieczor-retman@...el.com>,
Peter Newman <peternewman@...gle.com>,
James Morse <james.morse@....com>, Babu Moger <babu.moger@....com>,
Drew Fustini <dfustini@...libre.com>,
Dave Martin <Dave.Martin@....com>, linux-kernel@...r.kernel.org,
patches@...ts.linux.dev
Subject: Re: [PATCH 0/3] Add and use get_cpu_cacheinfo_level()
On Tue, Jun 04, 2024 at 07:22:50PM -0700, Andrew Morton wrote:
> 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.
Cool, thanks.
In general, you can safely ignore arch/x86/ patches. We're usually quick
to pick them up when ready. Getting them properly reviewed is a whole
another story... :-\
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists