From: linux@johnea.net
To: linux-omap@vger.kernel.org
Subject: Re: Which git to clone for testing prior to submitting bugs?
Date: Thu, 27 Sep 2012 11:56:51 -0700 [thread overview]
Message-ID: <5064A173.5000909@johnea.net> (raw)
In-Reply-To: <CAOCHtYitbhOMv+YBaYgdTuYZQpZ_VLoP=QKVS=spmqPxEUkATA@mail.gmail.com>
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?
Thanks again!
johnea
next prev parent reply other threads:[~2012-09-27 18:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 17:19 Which git to clone for testing prior to submitting bugs? linux
2012-09-27 18:25 ` Robert Nelson
2012-09-27 18:56 ` linux [this message]
2012-09-27 18:55 ` Felipe Balbi
2012-09-27 19:17 ` Tony Lindgren
2012-09-27 19:27 ` Robert Nelson
2012-09-27 19:39 ` Robert Nelson
2012-09-27 20:16 ` linux
2012-09-27 20:41 ` Robert Nelson
2012-09-28 18:49 ` linux
2012-09-28 19:18 ` Robert Nelson
2012-09-28 19:46 ` linux
2012-10-01 14:57 ` johnea
2012-10-01 16:50 ` Robert Nelson
2012-10-01 16:57 ` linux
2012-10-01 21:16 ` linux
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5064A173.5000909@johnea.net \
--to=linux@johnea.net \
--cc=linux-omap@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox