Re: [PATCH 2/2] ARM: multi_v7_defconfig: Replace USB_RCAR_GEN2_PHY by PHY_RCAR_GEN2

[Simon Horman <horms@verge.net.au>]

Hi Arnd, Hi Geert,

On Tue, May 12, 2015 at 09:42:40PM +0200, Arnd Bergmann wrote:
> On Tuesday 12 May 2015 18:30:59 Geert Uytterhoeven wrote:
> > 
> > I think Simon's question was more about asking what's the proper process
> > for updating multi_v7_defconfig.
> > 
> > Should this go through you / arm@kernel.org directly?
> > Should it go through arm subarchitecture maintainers, causing merge conflicts?
> 
> I think it should go through subarch maintainers, and we'll handle the
> conflicts as they arise when merging into the next/defconfig branch.
> This does mean that it's important to send the defconfig changes separately
> from other changes if possible, but it's fine to have a branch that touches
> both platform-specific and generic defconfig files.

Thanks, that is now completely clear to me.

FWIW, I am currently seeing one or two generic config changes per release
cycle. Which implies to me that conflicts should be minimal.

> > BTW, arm@kernel.org isn't documented in MAINTAINERS.
> 
> Right, that is intentional. We don't want to get Cc'd on 4000 patches per
> month that get sent to the mailing list for mach-*. By having a maintainer
> for each subdirectory and letting them decide what to forward to us,
> we're able to do our job better.
> 
> 	Arnd
>