From: Heiko Schocher <hs@denx.de>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: patches for 2.6.27... (Kumar Gala)
Date: Wed, 02 Jul 2008 11:58:03 +0200 [thread overview]
Message-ID: <486B512B.9000004@denx.de> (raw)
In-Reply-To: <mailman.486.1214989131.2883.linuxppc-dev@ozlabs.org>
Hello Kumar,
On Wednesday 02 July 2008, Kumar Gala wrote:
> Please point out any patches that have been posted but havent made it
> into a git tree related to Freescale chips.
Here are 2 patches that I'd like to see in 2.6.27. They haven't made into
any git tree as far as I know.
http://ozlabs.org/pipermail/linuxppc-dev/2008-June/058118.html
http://ozlabs.org/pipermail/linuxppc-dev/2008-June/057972.html
thanks.
bye
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next parent reply other threads:[~2008-07-02 9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.486.1214989131.2883.linuxppc-dev@ozlabs.org>
2008-07-02 9:58 ` Heiko Schocher [this message]
2008-08-06 6:58 ` patches for 2.6.27... (Kumar Gala) Heiko Schocher
2008-08-15 21:11 ` Wolfgang Denk
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=486B512B.9000004@denx.de \
--to=hs@denx.de \
--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 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).