mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	Rich Felker <dalias@libc.org>,
	linux-sh@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 6/7 v5] sh: fix Kconfig entry for NUMA => SMP
Date: Tue, 21 Mar 2023 08:16:38 -0700	[thread overview]
Message-ID: <02f8dade-e8ed-49b2-a2cf-aba4bcec0869@infradead.org> (raw)
In-Reply-To: <3a00d2b54f990e2fa18db722a81bea78402668c9.camel@physik.fu-berlin.de>



On 3/21/23 08:15, John Paul Adrian Glaubitz wrote:
> Hi Geert!
> 
> On Tue, 2023-03-21 at 09:47 +0100, Geert Uytterhoeven wrote:
>>> Yeah, this explains it then. Your new patch is definitely the better approach
>>> and I would prefer it over Randy's suggested change. Let's see what the mm
>>> maintainers have to say.
>>
>> I'm sure the missed condition was just an oversight, so I expect no
>> objections.
> 
> And you were right, of course. We can drop Randy's patch then, but I'll pick up
> all the other patches tomorrow when I prepare my for-next tree for 6.4.

Right, drop it.

Thanks, everyone.

-- 
~Randy

      reply	other threads:[~2023-03-21 15:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20 23:13 Randy Dunlap
2023-03-21  7:55 ` Geert Uytterhoeven
2023-03-21  8:10   ` John Paul Adrian Glaubitz
2023-03-21  8:19     ` Geert Uytterhoeven
2023-03-21  8:32       ` Geert Uytterhoeven
2023-03-21  8:38     ` D. Jeff Dionne
2023-03-21  8:42     ` Geert Uytterhoeven
2023-03-21  8:45       ` John Paul Adrian Glaubitz
2023-03-21  8:47         ` Geert Uytterhoeven
2023-03-21 15:15           ` John Paul Adrian Glaubitz
2023-03-21 15:16             ` Randy Dunlap [this message]

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=02f8dade-e8ed-49b2-a2cf-aba4bcec0869@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=dalias@libc.org \
    --cc=geert@linux-m68k.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=ysato@users.sourceforge.jp \
    /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

all inboxes | Powered by JetHome®