From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: "linuxppc-dev@ozlabs.org list" <linuxppc-dev@ozlabs.org>
Subject: Re: patches for 2.6.27...
Date: Thu, 3 Jul 2008 19:59:23 +0400 [thread overview]
Message-ID: <20080703155923.GA24286@polina.dev.rtsoft.ru> (raw)
In-Reply-To: <068935A1-11BE-4AEB-9C0E-E1AB53F1618E@kernel.crashing.org>
On Wed, Jul 02, 2008 at 02:56:16AM -0500, Kumar Gala wrote:
> Please point out any patches that have been posted but havent made it
> into a git tree related to Freescale chips.
How about RTC work for MPC8610HPCD/MPC8572DS:
[PATCH 1/4] powerpc: fsl_uli1575: fix RTC quirk to work on MPC8572DS and MPC8610HPCD
http://patchwork.ozlabs.org/linuxppc/patch?id=18913
[PATCH 2/4] powerpc/85xx/86xx: some refactoring for fsl_uli1575 code
http://patchwork.ozlabs.org/linuxppc/patch?id=18914
[PATCH 3/4] powerpc: rtc_cmos_setup: assign interrupts only if there is i8259 PIC
http://patchwork.ozlabs.org/linuxppc/patch?id=18915
[PATCH 4/4] powerpc/86xx: mpc8610_hpcd: add support for ULI RTC
http://patchwork.ozlabs.org/linuxppc/patch?id=18916
And mpc83xx_defconfig update for MPC8360E-RDK:
[PATCH v3] powerpc/83xx: update mpc83xx_defconfig to support MPC8360E-RDK
http://patchwork.ozlabs.org/linuxppc/patch?id=18903
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
next prev parent reply other threads:[~2008-07-03 15:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 7:56 patches for 2.6.27 Kumar Gala
2008-07-02 8:36 ` Laurent Pinchart
2008-07-06 14:54 ` Vitaly Bordug
2008-07-02 15:41 ` Scott Wood
2008-07-02 15:59 ` Kim Phillips
2008-07-04 22:33 ` Segher Boessenkool
2008-07-02 17:25 ` Dave Jiang
[not found] ` <200807021214.58080.pterry@vmetro.com>
2008-07-02 19:52 ` Kumar Gala
2008-07-03 15:59 ` Anton Vorontsov [this message]
2008-07-07 13:45 ` John Rigby
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=20080703155923.GA24286@polina.dev.rtsoft.ru \
--to=avorontsov@ru.mvista.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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.