From: Vitaly Bordug <vbordug@ru.mvista.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: [PATCH 0/3] 8560 && 8272 CPM-related fixes resubmit
Date: Wed, 24 Jan 2007 22:19:11 +0300 [thread overview]
Message-ID: <20070124191552.3033.93568.stgit@localhost.localdomain> (raw)
Paul,
All the points you've noticed are addressed here.
Fs-enet change has been sent over to netdev && Jeff, so is excluded from here
this round, as well as cpm-uart, that is mandatory for CPM1 only and hereby
will be folded into upcoming 8xx series.
--
Sincerely, Vitaly
next reply other threads:[~2007-01-24 21:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 19:19 Vitaly Bordug [this message]
2007-01-24 19:19 ` [PATCH 1/3] POWERPC] cpm2: CPM2 interrupt controller fix Vitaly Bordug
2007-01-24 21:56 ` Kumar Gala
2007-01-24 19:19 ` [PATCH 2/3] [POWERPC] Fix kernel build errors for mpc8272ads and mpc8560ads Vitaly Bordug
2007-01-24 19:19 ` [PATCH 3/3] [POWERPC] mpc8272ads: defconfig Vitaly Bordug
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=20070124191552.3033.93568.stgit@localhost.localdomain \
--to=vbordug@ru.mvista.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).