Doug Anderson wrote: > > Kukjin > > <take 2, not in HTML mode> > Oops, sorry. > On Thu, Jun 13, 2013 at 4:13 PM, Kukjin Kim <kgene.kim@xxxxxxxxxxx> wrote: > > Doug Anderson wrote: > >> > >> Tomasz, > >> > >> On Thu, Jun 13, 2013 at 9:42 AM, Tomasz Figa <tomasz.figa@xxxxxxxxx> > wrote: > >> >> > BTW, probably we need a similar fixing in the mach-exynos/common.c > >> >> > file > >> >> > before pinct기 for distro... > >> >> > >> >> Is anyone using the functions in mach-exynos/common.c file anymore? > I > >> >> thought that non-dt exynos support was going away and then we could > >> >> just delete a whole lot of code from that file. > >> > > >> > I think Kukjin meant stable kernels that support Exynos boards using > >> board > >> > files and without pinctrl. Would make sense to have them fixed as > well, > >> I > >> > guess. > >> > > Yes, correct. Thanks, Tomasz. > > > >> Ah, makes sense. Kukjin: do you know of someone who needs this > >> (someone who is picking up linux-stable updates for exynos)? I don't > >> think it's important for ChromeOS for this particular patch. If > >> there's someone who needs this to officially land on linux-stable I'd > >> be happy to review their backport of this patch. > >> > > As you know, developing something like Android, Tizen use the stable > kernel (long-term? I'm not sure) and there was a problem about this issue. > So I mean, would be fixed for the stable kernel. > > Sure, but do they actually pull in from linux-stable periodically? > I'd imagine that they have a private tree and that it would be their > job to backport any fixes onto their kernel. Right, the projects usually pull the linux-stable kernel when it starts. But as far as I know, they pick up some fixes from linux-stable during developing. Or for next project, would be better. I'm not sure what version will be used next time but it's obvious it will not be latest mainline :-) Thanks, - Kukjin -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |