Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20221004143901.130935-1-mpfj@newflow.co.uk> <CAAbcLfiCoa=-20cydPG9=42G9npaeBOCRXPPPTwkNFU-3yGoCg@mail.gmail.com>
 <20221108194742.0d9340f4@aktux> <Y2tYoHSFdJzrp9MW@atomide.com>
In-Reply-To: <Y2tYoHSFdJzrp9MW@atomide.com>
From:   Mark Jackson <mpfj@newflow.co.uk>
Date:   Wed, 9 Nov 2022 14:44:39 +0000
Message-ID: <CAAbcLfgYr1gfHNSycDc142aPuNUzxvhQ0GTyvExmMLa36e1nWg@mail.gmail.com>
Subject: Re: [PATCH] Update Nanobone
To:     Tony Lindgren <tony@atomide.com>
Cc:     Andreas Kemnade <andreas@kemnade.info>,
        linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Wed, 9 Nov 2022 at 07:37, Tony Lindgren <tony@atomide.com> wrote:
>
> The separate defconfig should not be needed. Please send any defconfig
> changes to multi_v7_defconfig or omap2plu_defconfig as separate patches.
>
> Note that you can run make savedefconfig first to produce a minimal diff.
> Then if adding device drivers, please add them as loadable modules where
> possible.

But using the omap2plus_defconfig increases my kernel to 4.7MB

My "custom" one has been specifically designed for the NANO platform
and currently sits at about 3.7MB (which nicely fits into the ~4MB memory
bank allocated to the kernel)

Hence the use of my custom defconfig.

I don't have modules enabled as the platform functionality is pretty fixed.

The defconfig I posted was created using savedefconfig.
Is it still wrong ?

Cheers
Mark J.