Re: [PATCH v6 11/11] arm/arm64: defconfig: Update configs to use the new CROS_EC options

[Lee Jones]

On Tue, 27 Aug 2019, Arnd Bergmann wrote:

> On Tue, Aug 27, 2019 at 4:52 PM Enric Balletbo i Serra
> <enric.balletbo@xxxxxxxxxxxxx> wrote:
> >
> > Hi,
> >
> > On 23/8/19 14:53, Enric Balletbo i Serra wrote:
> > > Recently we refactored the CrOS EC drivers moving part of the code from
> > > the MFD subsystem to the platform chrome subsystem. During this change
> > > we needed to rename some config options, so, update the defconfigs
> > > accordingly.
> > >
> > > Signed-off-by: Enric Balletbo i Serra <enric.balletbo@xxxxxxxxxxxxx>
> > > Acked-by: Krzysztof Kozlowski <krzk@xxxxxxxxxx>
> > > Reviewed-by: Gwendal Grignou <gwendal@xxxxxxxxxxxx>
> > > Tested-by: Gwendal Grignou <gwendal@xxxxxxxxxxxx>
> > > Acked-for-MFD-by: Lee Jones <lee.jones@xxxxxxxxxx>
> > > ---
> >
> >
> > For some reason I reduced too much the recipients from the get_maintainers
> > script and I missed the defconfig maintainers. Sorry about that, so cc'ing Arnd,
> > Olof, Will and Catalin
> >
> > To give you some context the full series can be found here [1].
> >
> > All the patches in the series are acked and will go through the MFD tree (Lee
> > Jones). This specific patch is still missing some acks from arm/arm64 defconfigs
> > and if you are agree can go through the Lee's tree with your acks, otherwise can
> > go through another tree.
> 
> Defconfig changes often cause merge conflicts, so I'd prefer to have
> this merged through the arm-soc tree. Can you resend the latest patch
> with the Acks to 'soc@xxxxxxxxxx' to get it into our patchwork?

How do you plan to keep this change-set bisectable?

Ideally the defconfg changes should really be paired with the re-work.
I was planning on creating an immutable branch for each of the
stakeholders to pull from.

-- 
Lee Jones [æçæ]
Linaro Services Technical Lead
Linaro.org â Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog