From: Florian Fainelli <florian.fainelli@broadcom.com>
To: "J. Neuschäfer" <j.neuschaefer@gmx.net>,
"Stefan Wahren" <wahrenst@gmx.net>
Cc: Russell King <linux@armlinux.org.uk>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
linux-arm-kernel@lists.infradead.org,
linux-rpi-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] ARM: bcm2835_defconfig: Enable SMP support
Date: Thu, 10 Oct 2024 15:47:49 -0700 [thread overview]
Message-ID: <4346e237-2dfa-4779-a6d9-99d747fad9c1@broadcom.com> (raw)
In-Reply-To: <Zo2Qexs-J5_Lzbjm@probook>
On 7/9/24 12:33, J. Neuschäfer wrote:
> On Mon, Jul 08, 2024 at 05:54:25PM +0200, Stefan Wahren wrote:
>> Hi Jonathan,
>>
>> Am 07.07.24 um 23:48 schrieb Jonathan Neuschäfer:
>>> Since there is only one Raspberry Pi related defconfig in the mainline
>>> kernel, it's useful to have to work well on all 32-bit Raspberry Pis.
>> this wasn't intention of bcm2835_defconfig. It's more focused on BCM2835
>> SOC and kernel-ci (both non-SMP). If you want to use the BCM2836 &
>> BCM2837 (incl. SMP), please use multi_v7_defconfig instead. Applying
>> this change would decrease the test coverage.
>
> Ah, fair enough.
It is fair that CONFIG_SMP_ON_UP is different from not enabling
CONFIG_SMP, but if we care to test CONFIG_SMP disabled, should not there
be a specific modification of multi_v7_defconfig or another
configuration specifically for that purpose?
--
Florian
prev parent reply other threads:[~2024-10-10 22:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-07 21:48 [PATCH 0/2] ARM: Refresh Raspberry Pi defconfig and enable " Jonathan Neuschäfer
2024-07-07 21:48 ` [PATCH 1/2] ARM: Refresh bcm2835_defconfig Jonathan Neuschäfer
2024-10-10 22:48 ` Florian Fainelli
2024-10-10 23:03 ` Stefan Wahren
2024-07-07 21:48 ` [PATCH 2/2] ARM: bcm2835_defconfig: Enable SMP support Jonathan Neuschäfer
2024-07-08 15:54 ` Stefan Wahren
2024-07-09 19:33 ` J. Neuschäfer
2024-10-10 22:47 ` Florian Fainelli [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=4346e237-2dfa-4779-a6d9-99d747fad9c1@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=j.neuschaefer@gmx.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=wahrenst@gmx.net \
/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®