On Wed, Nov 20, 2013 at 10:05 PM, Robert Yang <[email protected]> wrote: > > Hi Bruce, > > Thanks, we are going to update the kernel from 3.10.11 to 3.10.17 for dora > if there is no objections. > > Will we use another kernel source repo for dora ? Or just cherry-pick these > commits ?
Just do the cherry picks. The repository is safe for the dora branch. If that changes in the future, we can fork it into a new repo. Cheers, Bruce > > // Robert > > > On 11/19/2013 01:18 PM, Bruce Ashfield wrote: >> >> On Mon, Nov 18, 2013 at 10:34 PM, Robert Yang <[email protected]> >> wrote: >>> >>> >>> Hi Bruce, >>> >>> Here is the log status of the kernel layer between dora and master (18 >>> commits). >>> >>> I wonder are there any serious problems that we must upgrade it ? >>> >>> $ git log dora..master --abbrev-commit --pretty=oneline >>> meta/recipes-kernel >>> >>> 9a9a597 lttng-tools: Fixes incorrect path of ptest cases >>> e1e1ee5 linux-yocto/3.10: meta: ARM: OMAP3: Add USB PHY driver for >>> Beagleboard >>> 779dec9 linux-yocto-rt/3.10: fix ntp merge issue >>> 89c986c linux-yocto/3.10: meta: ARM: OMAP3: Add USB PHY driver for >>> Beagleboard >> >> >> You definitely want these. They fix USB and ethernet on the beagle >> >>> 8a03d59 sysvinit: adjust boot sequence and remove hack from udev >>> e9ec153 linux-yocto/3.10: fix qemuarm boot and spurious mips build >>> warning >>> baf005b linux-yocto/3.10: common-pc: add missing dependencies for >>> BRCMSMAC >>> dd361f0 linux-yocto/3.8: add crystalforest bsp legacy block drivers >>> configurations >>> 1fe7bca linux-yocto/3.10: haswell-wc and crystalforest support >> >> >> Don't worry about the "add support" here, they are benign to all other >> goards. >> >>> a23c7e9 linux-yocto-3.10: bump to 3.10.17 and -rt11 >> >> >> And this is where we need to be for the lttng fixes. >> >> The other updates are also safe, you can't really pick and chose. Just >> take all >> my SRCREV updates for 3.10 on master, since they are all bugfixes or minor >> meta-data tweaks so far. >> >> Bruce >> >>> 3129619 lttng-tools: make ptest able to work on target >>> 5e42796 recipes: Remove PR = r0 from all recipes >>> 2570f13 perf: flag __SANE_USERSPACE_TYPES__ to include int-ll64.h for >>> mips64 >>> 56cc2f2 linux-yocto/3.10: MinnowBoard support >>> db1d37a perf: flag __SANE_USERSPACE_TYPES__ to include int-ll64.h for >>> powerpc64 >>> cd414c0 kmod: Update to Rev 15 via git >>> e83640d kmod: Add patch to fix seperate build dir of ptest >>> 0f431a3 kmod-native: use bswap to work on older Linux hosts >>> >>> // Robert >>> >>> >>> On 11/18/2013 11:59 PM, Bruce Ashfield wrote: >>>> >>>> >>>> On 13-11-18 10:50 AM, Otavio Salvador wrote: >>>>> >>>>> >>>>> On Mon, Nov 18, 2013 at 1:31 PM, Saul Wold <[email protected]> wrote: >>>>>> >>>>>> >>>>>> On 11/18/2013 06:50 AM, Robert Yang wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 11/18/2013 10:18 PM, Otavio Salvador wrote: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Mon, Nov 18, 2013 at 10:25 AM, Robert Yang >>>>>>>> <[email protected]> wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> This should be considered for Dora as well as it fixes the >>>>>>>>>> deadlock >>>>>>>>>> and building with 3.12 kernels. >>>>>>>>>> >>>>>>>>> >>>>>>>>> Hi Otavio, thanks for suggesting this for dora, but dora's kernel >>>>>>>>> is >>>>>>>>> 3.10.11, >>>>>>>>> and this is an update for lttng-modules, I'm not sure whether dora >>>>>>>>> needs >>>>>>>>> this. >>>>>>>>> >>>>>>>>> Add Saul in the CC list. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> I think Dora ought to get the new 3.10 kernel updates; this can go >>>>>>>> along side with it. >>>>>>>> >>>>>>> >>>>>>> Hi Otavio, >>>>>>> >>>>>>> I'm sorry, but I'm not sure whether we need update dora's kernel from >>>>>>> 3.10.11 >>>>>>> to 3.10.17, since we seldom do the package update for a stable >>>>>>> branch, >>>>>>> let's wait for others' comments:-). >>>>>>> >>>>>> This is correct, I do not think we will be updating the kernel for a >>>>>> stable >>>>>> branch. >>>>> >>>>> >>>>> >>>>> This is wrong. We should update to 3.10.17 as this is the LTS release, >>>>> otherwise what is the point of us using a LTS at all? >>>> >>>> >>>> >>>> Obviously I'll be maintaining the LTS release in master, but that >>>> maintenance gets a mix of bug fixes and features associated with the >>>> upstream maintenance + LTSI + BSP requirements. >>>> >>>> I've sent patches for the sustained branches in the past, and can >>>> do it here as well. But to do it properly, there really needs to be a >>>> dedicated kernel repository, since things like the LTSI import and >>>> new BSP support will be mixed into the tree if a single 3.10 repo >>>> is used. >>>> >>>> I'm willing to split the repo and do -stable korg release updates, but >>>> at some point there are only so many repositories and versions that >>>> should be maintained at one time. As to what that number is, I don't >>>> have >>>> a firm one in mind. >>>> >>>> At a minimum, it would be safe for the dora maintenance branch to take >>>> my latest kernel -stable imports, but in the not to distant future, >>>> it would need a separate maintenance stream. >>>> >>>> Cheers, >>>> >>>> Bruce >>>> >>>>> >>>> >>>> >>>> >>> _______________________________________________ >>> Openembedded-core mailing list >>> [email protected] >>> http://lists.openembedded.org/mailman/listinfo/openembedded-core >> >> >> >> > -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
