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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 09/27/2012 11:25 AM, Robert Nelson wrote:
On Thu, Sep 27, 2012 at 12:19 PM,<linux@xxxxxxxxxx>  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?

Thanks again!

johnea

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux