mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Wahren <wahrenst@gmx.net>
To: "Florian Fainelli" <florian.fainelli@broadcom.com>,
	"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
	"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>,
	"Stefan Wahren" <stefan.wahren@i2se.com>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-rpi-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] ARM: Refresh bcm2835_defconfig
Date: Fri, 11 Oct 2024 01:03:15 +0200	[thread overview]
Message-ID: <00b1cce0-2d8f-4cd2-a89d-ae5387f79ebd@gmx.net> (raw)
In-Reply-To: <7fad6060-2466-4af4-b737-b3851d795023@broadcom.com>

Hi Florian,

Am 11.10.24 um 00:48 schrieb Florian Fainelli:
> On 7/7/24 14:48, Jonathan Neuschäfer wrote:
>> Regenerate bcm2835_defconfig with "make savedefconfig" in order to pick
>> up Kconfig changes that happened since the last refresh.
>>
>> Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
>
> Stefan, any objections to taking this change in isolation?
sure this would apply, but isn't this outdated yet?

Btw please look at

https://lore.kernel.org/linux-arm-kernel/20240910-fix-riscv-rt_group_sched-v3-4-486e75e5ae6d@gmail.com/

  reply	other threads:[~2024-10-10 23:03 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 SMP support 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 [this message]
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

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=00b1cce0-2d8f-4cd2-a89d-ae5387f79ebd@gmx.net \
    --to=wahrenst@gmx.net \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=florian.fainelli@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=stefan.wahren@i2se.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 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®