From: Kumar Gala <galak@kernel.crashing.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Please pull from 'powerpc-next' branch (for 2.6.27)(updated)
Date: Mon, 28 Jul 2008 08:50:04 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0807280849280.3813@blarg.am.freescale.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0807280752420.22887@blarg.am.freescale.net>
Please pull from 'powerpc-next' branch of
master.kernel.org:/pub/scm/linux/kernel/git/galak/powerpc.git powerpc-next
Laurent informed me I missed one CPM related patch:
'cpm2: Rework baud rate generators configuration to support external
clocks.'
- k
to receive the following updates:
Documentation/powerpc/dts-bindings/fsl/cpm_qe/serial.txt | 11
arch/powerpc/platforms/8xx/Kconfig | 10
arch/powerpc/platforms/Kconfig | 3
arch/powerpc/sysdev/cpm1.c | 267 ++++++++++++++-
arch/powerpc/sysdev/cpm2.c | 45 --
arch/powerpc/sysdev/cpm_common.c | 123 ++++++
arch/powerpc/sysdev/rtc_cmos_setup.c | 23 -
drivers/serial/cpm_uart/cpm_uart.h | 11
drivers/serial/cpm_uart/cpm_uart_core.c | 66 +++
include/asm-powerpc/cpm.h | 3
include/asm-powerpc/cpm2.h | 46 +-
11 files changed, 544 insertions(+), 64 deletions(-)
Anton Vorontsov (1):
powerpc: rtc_cmos_setup: assign interrupts only if there is i8259 PIC
Jochen Friedrich (1):
powerpc: implement GPIO LIB API on CPM1 Freescale SoC.
Laurent Pinchart (4):
cpm2: Implement GPIO LIB API on CPM2 Freescale SoC.
cpm_uart: Modem control lines support
cpm_uart: Add generic clock API support to set baudrates
cpm2: Rework baud rate generators configuration to support external clocks.
prev parent reply other threads:[~2008-07-28 13:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 12:54 Please pull from 'powerpc-next' branch (for 2.6.27) Kumar Gala
2008-07-28 13:50 ` Kumar Gala [this message]
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=Pine.LNX.4.64.0807280849280.3813@blarg.am.freescale.net \
--to=galak@kernel.crashing.org \
--cc=benh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).