Re: [PATCH v5][resend v4] of: replace Asahi Kasei Corp vendor prefix

[Arnd Bergmann]

On Friday 09 January 2015 07:46:16 Rob Herring wrote:
> On Fri, Jan 9, 2015 at 4:07 AM, Kuninori Morimoto
> <kuninori.morimoto.gx@xxxxxxxxxxx> wrote:
> >
> > Hi Stephen
> >
> > Thank you for your feedback
> >
> >> > I'm sending this "of: replace Asahi Kasei Corp vendor prefix" during
> >> > half-year (since Jun 2014) , many times. But, no-one care it.
> >> > I don't know who is the best maintainer.
> >> >  - Stephen : because it has Tegra ?
> >> >  - Olof    : because it has Tegra (= ARM) ?
> >> >  - Arnd    : because it has Tegra (= ARM) ?
> >> >  - Matthias: because it has Tegra (= ARM SoC) ?
> >> >  - Rob     : because DT ?
> >> >  - Andrew  : Last chance ?
> >> >
> >> > But, could you please care this patch ?
> >> > I will re-send it again
> >>
> >> It doesn't seem to be ack'd by any of the DT maintainers. Retro-actively
> >> changing a DT vendor name would need that, I think.
> >
> > Rob ?
> > I had sent this patch to him since half-years ago, many times...
> > Or other maintainer ?
> >
> >> Thierry and Alex (both Tegra maintainers) appear to have ack'd it, so it
> >> seems they expect it to go through some tree other than Tegra. Weren't
> >> there a bunch of related patches along with this (e.g. updating relevant
> >> drivers to support both prefixes?) so it was expected this patch would
> >> be applied together with them?
> >
> > I guess they expected it goes to DT branch (?)
> > This is only 1 patch. it doesn't have related patch-set
> 
> It is in my queue. If the users of it are fine with breaking things,
> who am I to argue with them.

It's an i2c device, so it won't break, based on the implementation
we use in the kernel that ignores the vendor part when the part number
matches the i2c driver name.

I also don't think we need to worry about any non-Linux operating
systems on this board that might share the same dts file.

	Arnd
--
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/