From: Remy Bohmer <linux@bohmer.net>
To: Ravi Kumar Kulkarni <ravikulkarni@asladvancedsys.in>
Cc: linux-kernel@vger.kernel.org, linux@maxim.org.za
Subject: Re: Info on AT91 patches against mainline kernel
Date: Fri, 5 Mar 2010 15:34:06 +0100 [thread overview]
Message-ID: <3efb10971003050634o37807a22tccd5c9416f3eb7a@mail.gmail.com> (raw)
In-Reply-To: <4B90E415.5090106@asladvancedsys.in>
Hi,
2010/3/5 Ravi Kumar Kulkarni <ravikulkarni@asladvancedsys.in>:
> Hi Remy,
>>
>> You do not necessarily need the at91-patchset from Andrew.
>> 2.6.33 works fine on at91sam9261 without it...
>>
>> Remy
>>
>
> Thanks for the info. I will try to compile 2.6.33 now. But i got a mail
> from andrew that he updated at91 patchset to 2.6.32 . for clarification jus
> verifying tat u mean from 2.6.33 onwards u don't need at91 patches and
> can directly compile without waiting Andrew's patchset . If tats case then
> Andrew can update that in linux4samdotorg website so that it will be helpful
You only need the changes from Andrew in case there is something in
there that you require, you should look at the changelog to be sure.
But, the at91sam9261 is already for several years in mainline and it
works fine (even much older kernels than 2.6.33 will work without it,
for example we used 2.6.24, 2.6.26, 2.6.31 without it), Andrews
patchset is just a set of additional changes that will likely be
pushed to mainline at some time.
Remy
next prev parent reply other threads:[~2010-03-05 14:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 14:19 Ravi Kumar Kulkarni
2010-03-05 10:29 ` Remy Bohmer
2010-03-05 10:59 ` Ravi Kumar Kulkarni
2010-03-05 14:34 ` Remy Bohmer [this message]
2010-03-08 4:19 ` Ravi Kumar Kulkarni
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=3efb10971003050634o37807a22tccd5c9416f3eb7a@mail.gmail.com \
--to=linux@bohmer.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@maxim.org.za \
--cc=ravikulkarni@asladvancedsys.in \
/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
all inboxes | Powered by JetHome®