From: Sekhar Nori <nsekhar@ti.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
ARM-SoC Maintainers <arm@kernel.org>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL 2/4] DaVinci defconfig updates for v5.4
Date: Thu, 5 Sep 2019 11:47:55 +0530 [thread overview]
Message-ID: <937b7ee1-ebdd-220d-f43a-da5e40ddfdf3@ti.com> (raw)
In-Reply-To: <CAK8P3a0NGVHhWBtXwbB7aZMA-hsGn-jwJDYUS1WgLoux6j-hBA@mail.gmail.com>
Hi Arnd,
On 04/09/19 8:21 PM, Arnd Bergmann wrote:
> On Wed, Aug 28, 2019 at 5:18 PM Sekhar Nori <nsekhar@ti.com> wrote:
>>
>> The following changes since commit 5f9e832c137075045d15cd6899ab0505cfb2ca4b:
>>
>> Linus 5.3-rc1 (2019-07-21 14:05:38 -0700)
>>
>> are available in the Git repository at:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/nsekhar/linux-davinci.git tags/davinci-for-v5.4/defconfig
>>
>> for you to fetch changes up to e869e44f2d82b9b4d35d58ceaeeadb0242bc634c:
>>
>> ARM: davinci_all_defconfig: enable GPIO backlight (2019-08-08 14:33:45 +0530)
>>
>> ----------------------------------------------------------------
>> Contains davinci_all_defconfig refresh using savedefconfig and a
>> patch to enable GPIO backlight.
>>
>> ----------------------------------------------------------------
>> Bartosz Golaszewski (2):
>> ARM: davinci: refresh davinci_all_defconfig
>> ARM: davinci_all_defconfig: enable GPIO backlight
>
> I'm generally not a fan of these 'refresh defconfig' patches when they
> silently change options that may or may not be needed.
You are right, I should have watched the output more closely. Since this
is something someone doing 'make davinci_all_defconfig' already sees, I
tend to skip the actual patch output.
>
> Some lines are just moved around but these ones
> are completely removed:
>
> -# CONFIG_IOSCHED_DEADLINE is not set
> -# CONFIG_IOSCHED_CFQ is not set
> -CONFIG_PREEMPT=y
> -CONFIG_SND_SOC_TLV320AIC3X=m
> -CONFIG_SND_SOC_DAVINCI_MCASP=m
> -CONFIG_LEDS_TRIGGERS=y
> -CONFIG_TI_EDMA=y
> -# CONFIG_ARM_UNWIND is not set
>
> I think most of these are ok, but I don't see any explanation
> about why you turn off CONFIG_PREEMPT.
So this came because with commit a50a3f4b6a31 ("sched/rt, Kconfig:
Introduce CONFIG_PREEMPT_RT") PREEMPT lost its prompt string. As
suggested by that commit, davinci_all_defconfig should be enabling
CONFIG_PREEMPT_LL=y to retain functionality.
I can respin the branch with the preempt fix first and then the
defconfig refresh. Or I can skip the refresh altogether.
Thanks,
Sekhar
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-09-05 6:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 15:17 [GIT PULL 1/4] DaVinci SoC updates for v5.4 Sekhar Nori
2019-08-28 15:17 ` [GIT PULL 2/4] DaVinci defconfig " Sekhar Nori
2019-09-04 14:51 ` Arnd Bergmann
2019-09-05 6:17 ` Sekhar Nori [this message]
2019-09-05 9:15 ` Arnd Bergmann
2019-09-06 6:31 ` Peter Ujfalusi
2019-09-06 8:46 ` Arnd Bergmann
2019-08-28 15:17 ` [GIT PULL 3/4] DaVinci fbdev driver " Sekhar Nori
2019-09-04 14:56 ` Arnd Bergmann
2019-08-28 15:17 ` [GIT PULL 4/4] DaVinci DT " Sekhar Nori
2019-09-04 14:57 ` Arnd Bergmann
2019-09-04 13:24 ` [GIT PULL 1/4] DaVinci SoC " Arnd Bergmann
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=937b7ee1-ebdd-220d-f43a-da5e40ddfdf3@ti.com \
--to=nsekhar@ti.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=bgolaszewski@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox