From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 RFT] ARM: bcm2835: enable all bcm2835-relevant in defconfig
Date: Mon, 26 Oct 2015 20:03:04 -0600 [thread overview]
Message-ID: <562EDB58.4000001@wwwdotorg.org> (raw)
In-Reply-To: <562C8E6C.7030205@lategoodbye.de>
On 10/25/2015 02:10 AM, Stefan Wahren wrote:
> Am 25.10.2015 um 04:48 schrieb Stephen Warren:
>> On 10/15/2015 03:57 PM, Stefan Wahren wrote:
>>> Rebuild bcm2835_defconfig using "make bcm2835_defconfig;
>>> make savedefconfig", and enable manually the following features:
>>>
>>> * all bcm2835-relevant drivers (MBOX, WDT, DMA, PWM, SND)
>>> * enable regular stackprotector because CONFIG_CC_STACKPROTECTOR
>>> disappear
>>> * enable some new dependencies in order to keep LED heartbeat
>>> ( CONFIG_NEW_LEDS, CONFIG_LEDS_CLASS, CONFIG_LEDS_TRIGGERS )
>>
>>> diff --git a/arch/arm/configs/bcm2835_defconfig
>>> b/arch/arm/configs/bcm2835_defconfig
>>
>>> -CONFIG_RESOURCE_COUNTERS=y
>
> This option becomes obsolete:
>
> kernel: res_counter: remove the unused API
>
> 5b1efc027c0b51ca3e76f4e00c83358f8349f543
>
>>> -CONFIG_RD_BZIP2=y
>>> -CONFIG_RD_LZMA=y
>>> -CONFIG_RD_XZ=y
>>> -CONFIG_RD_LZO=y
>
> These are enabled implicit.
>
>>> -CONFIG_SCSI_MULTI_LUN=y
>
> This option becomes obsolete:
>
> scsi: Remove CONFIG_SCSI_MULTI_LUN
>
> c309b35171ddb5384cc3f2f9dc82a96dccc6b7f6
>
>>> -CONFIG_USB_DWC2_HOST=y
>>> -CONFIG_EXT4_FS=y
>>> -CONFIG_EXT4_FS_POSIX_ACL=y
>
> These are enabled implicit.
>
>>
>> Do you know why all of those were removed?
The explanations sound good. It'd be useful to have that kind of thing
explained in the commit message for any future patches.
prev parent reply other threads:[~2015-10-27 2:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 21:57 [PATCH V2 RFT] ARM: bcm2835: enable all bcm2835-relevant in defconfig Stefan Wahren
2015-10-25 3:48 ` Stephen Warren
2015-10-25 8:10 ` Stefan Wahren
2015-10-27 2:03 ` Stephen Warren [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=562EDB58.4000001@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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;
as well as URLs for NNTP newsgroup(s).