Re: [PATCH 0/9] multi_v7_defconfig: Enable options for Exynos Chromebooks

From: Kukjin Kim
Date: Fri May 15 2015 - 23:25:30 EST


On 05/15/15 21:00, Krzysztof Kozlowski wrote:
> 2015-05-15 20:37 GMT+09:00 Arnd Bergmann <arnd@xxxxxxxx>:
>> On Thursday 14 May 2015 17:40:07 Javier Martinez Canillas wrote:
>>> Hello arm-soc maintainers,
>>>
>>> This series is an attempt to reduce the delta between exynos_defconfig
>>> and multi_v7_defconfig. Primarily to enable the needed Kconfig symbols
>>> to make all Exynos Chromebooks peripherals to be working when building
>>> an image using the ARMv7 multi-platform default config.
>>>
>>> Since the policy is now to now enable as much as possible, I did build
>>> as a module all the Kconfig symbols that were tristate and only enable
>>> as built-in those that can't be a module because are boolean options.
>>>
>>> A nice side effect of this series is that I found that many drivers
>>> were not working properly when built as a module because the modalias
>>> information was not filled properly or at all. I've posted patches to
>>> fix the issues I found when testing this series.
>>>
>>> The patches have been tested on an Exynos5250 Snow, Exynos5420 Peach
>>> Pit and Exynos5800 Peach Pi Chromebooks but most config options will
>>> be useful for others Exynos5 or other Samsung SoCs.
>>>
>>> The series is composed of the following patches that can be applied on
>>> top of your next/defconfig branch [0].
>>
>> Looks good to me. My preferred approach for merging would be to have
>> Kukjin pick up these patches and send a pull request, along with other
>> defconfig changes he might have for exynos.
>
OK, I'll in this weekend.

> I have some other old patches in the same topic - related to important
> stuff for Exynos boards. I'll rebase them and ask Kukjin for picking.
>
Yeah, OK.

Thanks,
Kukjin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/