Message ID | 20190203212936.17053-1-vz@mleia.com (mailing list archive) |
---|---|
State | Mainlined, archived |
Commit | 25dc2e0bd22ecf7be552c44a71c0abe68f6a641d |
Headers | show |
Series | [GIT,PULL,1/3] ARM: defconfig: NXP LPC32xx and LPC18xx/LPC43xx changes for 5.1 | expand |
On Sun, Feb 3, 2019 at 10:29 PM Vladimir Zapolskiy <vz@mleia.com> wrote: > > Hi Arnd, Olof and Kevin, > > please consider to pull the updates to NXP LPC32xx and NXP LPC18xx/LPC32xx > defconfig files, both defconfigs are now up to date to provide support of > boards maintained in the Linux kernel and savedefconfig does not produce > a difference. > > The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c: > > Linux 5.0-rc1 (2019-01-06 17:08:20 -0800) > > are available in the Git repository at: > > https://github.com/vzapolskiy/linux-lpc32xx tags/lpc32xx-defconfig-for-5.1 > > for you to fetch changes up to 25dc2e0bd22ecf7be552c44a71c0abe68f6a641d: > > ARM: defconfig: lpc32xx: enable DRM simple panel driver (2019-02-03 21:25:42 +0200) > > ---------------------------------------------------------------- > ARM: lpc32xx: defconfig updates for v5.1 > > Here are the changes for ARM NXP LPC32xx and ARM NXP LPC18xx/LPC43xx > defconfig files: > * LPC18xx/LPC43xx and LPC32xx defconfig files got updates to match > savedefconfig, > * PL11x LCD controller driver on both LPC18xx/LPC43xx and LPC32xx > has been switched from fbdev to DRM one, > * drivers of GPIO controllers not found on LPC32xx boards are disabled, > * LPC32xx gets enabled additional sane debugging options: panic on oops, > sysrq, dynamic debug, timestamps in kernel log buffer and built GDB > scripts, > * LPC32xx gets enabled NFSv4 support, > * LPC32xx gets enabled a number of used drivers: DRM simple panel, > fixed voltage regulator and generic SRAM drivers, > * Option to have a serial console on HS UART on LPC32xx is enabled. Pulled into arm/defconfig. It took me a bit of time to check that the refreshing of the defconfigs did not have any side-effects that went unnoticed. It's better to split those up further into patches that either only move around options, or drop options with explanations of what happened. For the newly added options, I wouldn't mind doing the reverse and enabling everything at once with the combined changelog. Thanks, Arnd