From: Vitaly Bordug <vbordug@ru.mvista.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: [PATCH 0/4] CPM-related stuff resubmit
Date: Tue, 12 Dec 2006 01:36:12 +0300 [thread overview]
Message-ID: <20061212013612.18725c25@localhost.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 555 bytes --]
Paul,
Resubmit with proper Sign-off follows. Those fixes are more or less
independent by sense, but here they are in order I applied them to prevent confusion.
Fs_enet patch, as usual, included as reference and to represent a full picture, and will be sent
over to netdev.
They were applied after the 8xx series in my tree, and though I haven't validated each one for
self-sufficiency, they play nicely in a row. I don't think they'll confuse because of linus' merge
either, if so, let me know and I'll do a rebase.
--
Thanks, Vitaly
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2006-12-11 22:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20061212013612.18725c25@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).