All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: Justin Forbes <jforbes@fedoraproject.org>,
	Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, jmforbes@linuxtx.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Revert arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER
Date: Tue, 2 May 2023 18:40:14 +0100	[thread overview]
Message-ID: <ZFFK/qPTCIpGE2Tu@arm.com> (raw)
In-Reply-To: <ZFE3GDjmUWpMpmqu@kernel.org>

On Tue, May 02, 2023 at 07:15:20PM +0300, Mike Rapoport wrote:
> On Tue, May 02, 2023 at 03:07:41PM +0100, Catalin Marinas wrote:
> > On Mon, May 01, 2023 at 04:24:38PM -0500, Justin Forbes wrote:
> > 
> > Regarding EXPERT, we could drop it and do like the other architectures
> > but we'll have randconfig occasionally hitting weird values that won't
> > build (like -1). Not sure EXPERT helps here.
> 
> AFAIU, randconfig does not randomize int values, it's probably random
> people that do ;-)

https://lore.kernel.org/r/202303232149.Chh6KhiI-lkp@intel.com

with the randconfig here:

https://download.01.org/0day-ci/archive/20230323/202303232149.Chh6KhiI-lkp@intel.com/config

That said, it would fail on other architectures as well, maybe they are
just not wired up in the build machines.

-- 
Catalin

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: Justin Forbes <jforbes@fedoraproject.org>,
	Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, jmforbes@linuxtx.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Revert arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER
Date: Tue, 2 May 2023 18:40:14 +0100	[thread overview]
Message-ID: <ZFFK/qPTCIpGE2Tu@arm.com> (raw)
In-Reply-To: <ZFE3GDjmUWpMpmqu@kernel.org>

On Tue, May 02, 2023 at 07:15:20PM +0300, Mike Rapoport wrote:
> On Tue, May 02, 2023 at 03:07:41PM +0100, Catalin Marinas wrote:
> > On Mon, May 01, 2023 at 04:24:38PM -0500, Justin Forbes wrote:
> > 
> > Regarding EXPERT, we could drop it and do like the other architectures
> > but we'll have randconfig occasionally hitting weird values that won't
> > build (like -1). Not sure EXPERT helps here.
> 
> AFAIU, randconfig does not randomize int values, it's probably random
> people that do ;-)

https://lore.kernel.org/r/202303232149.Chh6KhiI-lkp@intel.com

with the randconfig here:

https://download.01.org/0day-ci/archive/20230323/202303232149.Chh6KhiI-lkp@intel.com/config

That said, it would fail on other architectures as well, maybe they are
just not wired up in the build machines.

-- 
Catalin

  reply	other threads:[~2023-05-02 17:41 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-28 15:36 [PATCH] Revert arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER Justin M. Forbes
2023-04-28 15:36 ` Justin M. Forbes
2023-04-28 17:01 ` Catalin Marinas
2023-04-28 17:01   ` Catalin Marinas
2023-04-29 19:01   ` Mike Rapoport
2023-04-29 19:01     ` Mike Rapoport
2023-04-29 22:42     ` Justin Forbes
2023-04-29 22:42       ` Justin Forbes
2023-04-30  3:54       ` Mike Rapoport
2023-04-30  3:54         ` Mike Rapoport
2023-05-01 21:24         ` Justin Forbes
2023-05-01 21:24           ` Justin Forbes
2023-05-02 14:07           ` Catalin Marinas
2023-05-02 14:07             ` Catalin Marinas
2023-05-02 14:21             ` Marc Zyngier
2023-05-02 14:21               ` Marc Zyngier
2023-05-02 16:12               ` Mike Rapoport
2023-05-02 16:12                 ` Mike Rapoport
2023-05-02 16:15             ` Mike Rapoport
2023-05-02 16:15               ` Mike Rapoport
2023-05-02 17:40               ` Catalin Marinas [this message]
2023-05-02 17:40                 ` Catalin Marinas
2023-05-03 10:20                 ` Catalin Marinas
2023-05-03 10:20                   ` Catalin Marinas
2023-05-03 12:08                   ` Philip Li
2023-05-03 12:08                     ` Philip Li

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=ZFFK/qPTCIpGE2Tu@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=jforbes@fedoraproject.org \
    --cc=jmforbes@linuxtx.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rppt@kernel.org \
    --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 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.