Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Benjamin Herrenschmidt" <benh@kernel.crashing.org>,
	"Paul Mackerras" <paulus@samba.org>,
	"Michael Ellerman" <mpe@ellerman.id.au>,
	"alex@ghiti.fr" <alex@ghiti.fr>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
	"will@kernel.org" <will@kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Toan Le" <toan@os.amperecomputing.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH v8 01/14] sizes.h: Add SZ_1T macro
Date: Thu, 10 Mar 2022 18:09:51 +0000	[thread overview]
Message-ID: <969d885d-dcff-61b9-50cd-cdaf511505ab@csgroup.eu> (raw)
In-Reply-To: <20220310165206.GA163581@bhelgaas>



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@csgroup.eu>
>> Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
>> Reviewed-by: Krzysztof Wilczyński <kw@linux.com>
>> Acked-by: Bjorn Helgaas <bhelgaas@google.com>
>> Cc: Toan Le <toan@os.amperecomputing.com>
>> Cc: linux-pci@vger.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

  reply	other threads:[~2022-03-10 18:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1646847561.git.christophe.leroy@csgroup.eu>
2022-03-09 17:44 ` [PATCH v8 01/14] sizes.h: Add SZ_1T macro Christophe Leroy
2022-03-10 16:52   ` Bjorn Helgaas
2022-03-10 18:09     ` Christophe Leroy [this message]
2022-03-10 18:21       ` Bjorn Helgaas

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=969d885d-dcff-61b9-50cd-cdaf511505ab@csgroup.eu \
    --to=christophe.leroy@csgroup.eu \
    --cc=akpm@linux-foundation.org \
    --cc=alex@ghiti.fr \
    --cc=benh@kernel.crashing.org \
    --cc=bhelgaas@google.com \
    --cc=catalin.marinas@arm.com \
    --cc=helgaas@kernel.org \
    --cc=kw@linux.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=mpe@ellerman.id.au \
    --cc=paulus@samba.org \
    --cc=toan@os.amperecomputing.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