From: Segher Boessenkool <segher@kernel.crashing.org>
To: Kim Phillips <kim.phillips@freescale.com>
Cc: "linuxppc-dev@ozlabs.org list" <linuxppc-dev@ozlabs.org>
Subject: Re: patches for 2.6.27...
Date: Sat, 5 Jul 2008 00:33:22 +0200 [thread overview]
Message-ID: <78c76632ee8501c9a4974a9291689b8c@kernel.crashing.org> (raw)
In-Reply-To: <20080702105946.0ec1ffcc.kim.phillips@freescale.com>
>> Please point out any patches that have been posted but havent made it
>> into a git tree related to Freescale chips.
>
> I haven't heard back from Segher, so:
>
> http://patchwork.ozlabs.org/linuxppc/patch?id=19313
You haven't heard back because I feel like I'm talking to a wall.
The "compatible" definition for this node needs to be fixed.
Segher
next prev parent reply other threads:[~2008-07-04 22:33 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 [this message]
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
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=78c76632ee8501c9a4974a9291689b8c@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=kim.phillips@freescale.com \
--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).