From: marek.vasut@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: Best kernel to use and some patches...
Date: Tue, 3 Jan 2012 22:17:51 +0100 [thread overview]
Message-ID: <201201032217.51399.marek.vasut@gmail.com> (raw)
In-Reply-To: <CAEBDL5VPv=qmUBp0EZcQSff5sbcb8RqH1JkoktF0Qqu-=1BsRQ@mail.gmail.com>
> Hello Everyone,
>
> I hope this is the right forum for the this. On a project, we're
> currently using the 2.6.34 line of kernel. After running into some
> issues, we're looking at what to upgrade to for the next rev of our
> product. Is there a recommended version to use? Preferably one that
> has some kind of long-term support?
>
> Also, we ran into a cache-flushing issue in the 2.6.34 kernel with the
> MMC/SDCard subsystem. We're running 2.6.34, but the issue still
> exists in 2.6.34.10. Are you still taking patches for that line?
No, check stable kernel releases (hint: kernel.org, keyword "stable")
M
>
> Thanks!
>
> -John
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2012-01-03 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 19:27 Best kernel to use and some patches John Szakmeister
2012-01-03 21:17 ` Marek Vasut [this message]
2012-01-03 23:53 ` John Szakmeister
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=201201032217.51399.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.