Re: Which git to clone for testing prior to submitting bugs?

[Felipe Balbi <balbi@ti.com>]

[-- Attachment #1: Type: text/plain, Size: 1362 bytes --]

Hi,

On Thu, Sep 27, 2012 at 11:56:51AM -0700, linux@johnea.net wrote:
> On 09/27/2012 11:25 AM, Robert Nelson wrote:
> >On Thu, Sep 27, 2012 at 12:19 PM,<linux@johnea.net>  wrote:
> >>
> >>Hello,
> >>
> >>In a subsequent distro upgrade to 3.4.4 neither dvi, nor buddy=spidev
> >>function anymore.
> >
> >"buddy=xyz" is not upstream, so which 'tree'/'patchset' are you
> >currently using as a basis for your device?  The authors of that
> >patchset might be able to help out..
> >
> 
> Thanks Robert,
> 
> The 3.4.4 kernel is plain vanilla plus:
> 
> http://rcn-ee.net/deb/sid-armhf/v3.4.4-x1/patch-3.4.4-x1.diff.gz
> 
> We're running archlinuxarm, and working with devs there to upgrade to
> 3.5.4, in hopes this will address most or all of the issues. That will
> include:
> 
> http://rcn-ee.net/deb/sid-armhf/v3.5.4-x6/patch-3.5.4-x6.diff.gz
> 
> We adopted archlinux because it's about as close to a git kernel as
> can be had in a disto packaged format.
> 
> If we still experience issues, I'm trying to understand what to clone
> to be relevant to this list.
> 
> Which tree are patches submitted against here?

If you want to try with the public kernel, then try Linus' tree
(http://git.kernel.org/linus) but I'm not sure if we have beagle XM in
mainline yet.

Tony is DM3730 supported in mainline ?

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]