[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <969d885d-dcff-61b9-50cd-cdaf511505ab@csgroup.eu>
Date: Thu, 10 Mar 2022 18:09:51 +0000
From: Christophe Leroy <christophe.leroy@...roup.eu>
To: Bjorn Helgaas <helgaas@...nel.org>
CC: Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Paul Mackerras <paulus@...ba.org>,
Michael Ellerman <mpe@...erman.id.au>,
"alex@...ti.fr" <alex@...ti.fr>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"catalin.marinas@....com" <catalin.marinas@....com>,
"will@...nel.org" <will@...nel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
Krzysztof Wilczyński <kw@...ux.com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Toan Le <toan@...amperecomputing.com>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>
Subject: Re: [PATCH v8 01/14] sizes.h: Add SZ_1T macro
Le 10/03/2022 à 17:52, Bjorn Helgaas a écrit :
> On Wed, Mar 09, 2022 at 06:44:35PM +0100, Christophe Leroy wrote:
>> Today drivers/pci/controller/pci-xgene.c defines SZ_1T
>>
>> Move it into linux/sizes.h so that it can be re-used elsewhere.
>>
>> Link: https://lore.kernel.org/r/575cb7164cf124c75df7cb9242ea7374733942bf.1642752946.git.christophe.leroy@csgroup.eu
>> Signed-off-by: Christophe Leroy <christophe.leroy@...roup.eu>
>> Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@....com>
>> Reviewed-by: Krzysztof Wilczyński <kw@...ux.com>
>> Acked-by: Bjorn Helgaas <bhelgaas@...gle.com>
>> Cc: Toan Le <toan@...amperecomputing.com>
>> Cc: linux-pci@...r.kernel.org
>> ---
>> This patch is already in linux-next but not in Linus' tree yet
>
> What would you like me to do about this? It's in linux-next, which
> means it will go to Linus' tree during the next merge window.
>
> But this is 01/14; are there other patches that I should be looking
> at? Do I need to coordinate this with other patches that depend on
> it?
Yes sorry I should have said it. Patch 14/14 depends on it.
Don't know yet what's the merge strategy for this series, there as not
been any changes since v6 mid December and core parts are acked/reviewed
so I would be happy if at least core mm parts could go this cycle. I
sent a question to Michael and Andrew about it.
Christophe
Powered by blists - more mailing lists