All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Oscar Salvador <osalvador@suse.de>,
	Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Cc: linux-mm@kvack.org,
	Geetika Moolchandani <Geetika.Moolchandani1@ibm.com>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Michal Hocko <mhocko@kernel.org>
Subject: Re: [PATCH] powerpc/numa: Associate numa node to its cpu earlier
Date: Tue, 12 Apr 2022 00:00:46 +1000	[thread overview]
Message-ID: <87v8vf67ox.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <YlPznpqqPTI/KFNV@localhost.localdomain>

Oscar Salvador <osalvador@suse.de> writes:
> On Mon, Apr 11, 2022 at 02:28:08PM +0530, Srikar Dronamraju wrote:
>> Given that my patch got accepted into powerpc tree
>> https://git.kernel.org/powerpc/c/e4ff77598a109bd36789ad5e80aba66fc53d0ffb
>> is now part of Linus tree, this line may need a slight tweak.
>
> Right.
>
> @Michael: Will you resolve the conflict, or you would rather want me to send
> v2 with the amendment?

I can resolve the conflict, it should be trivial. If there's any trouble
I'll let you know.

cheers

WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <mpe@ellerman.id.au>
To: Oscar Salvador <osalvador@suse.de>,
	Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Geetika Moolchandani <Geetika.Moolchandani1@ibm.com>,
	Michal Hocko <mhocko@kernel.org>,
	linux-mm@kvack.org
Subject: Re: [PATCH] powerpc/numa: Associate numa node to its cpu earlier
Date: Tue, 12 Apr 2022 00:00:46 +1000	[thread overview]
Message-ID: <87v8vf67ox.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <YlPznpqqPTI/KFNV@localhost.localdomain>

Oscar Salvador <osalvador@suse.de> writes:
> On Mon, Apr 11, 2022 at 02:28:08PM +0530, Srikar Dronamraju wrote:
>> Given that my patch got accepted into powerpc tree
>> https://git.kernel.org/powerpc/c/e4ff77598a109bd36789ad5e80aba66fc53d0ffb
>> is now part of Linus tree, this line may need a slight tweak.
>
> Right.
>
> @Michael: Will you resolve the conflict, or you would rather want me to send
> v2 with the amendment?

I can resolve the conflict, it should be trivial. If there's any trouble
I'll let you know.

cheers


  reply	other threads:[~2022-04-11 14:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11  7:49 [PATCH] powerpc/numa: Associate numa node to its cpu earlier Oscar Salvador
2022-04-11  7:49 ` Oscar Salvador
2022-04-11  8:58 ` Srikar Dronamraju
2022-04-11  8:58   ` Srikar Dronamraju
2022-04-11  9:23   ` Oscar Salvador
2022-04-11  9:23     ` Oscar Salvador
2022-04-11 14:00     ` Michael Ellerman [this message]
2022-04-11 14:00       ` Michael Ellerman
2022-05-24 11:09 ` Michael Ellerman
2022-05-24 11:09   ` Michael Ellerman

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=87v8vf67ox.fsf@mpe.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=Geetika.Moolchandani1@ibm.com \
    --cc=linux-mm@kvack.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mhocko@kernel.org \
    --cc=osalvador@suse.de \
    --cc=srikar@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.