From: Paul Mackerras <paulus@samba.org>
To: Jeremy Kerr <jk@ozlabs.org>
Cc: linuxppc-dev@ozlabs.org, cbe-oss-dev@ozlabs.org, netdev@oss.sgi.com
Subject: Re: [PATCH 15/20] [powerpc, netdevices] Constify & voidify get_property()
Date: Fri, 7 Jul 2006 20:35:14 +1000 [thread overview]
Message-ID: <17582.14562.991790.920984@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <98457831@toto.iv>
Jeremy Kerr writes:
> powerpc-specific network device driver changes.
For some reason, the whitespace got munged on this one. There were
some rejects on some of the other patches due to some of Ben H's
patches. Please fix them and move the include/linux/platform_device.h
change into the same patch as the drivers/base/platform.c change.
I have applied patches 1-3. Please resubmit the rest.
Regards,
Paul.
next parent reply other threads:[~2006-07-07 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <98457831@toto.iv>
2006-07-07 10:35 ` Paul Mackerras [this message]
2006-07-10 3:40 ` [PATCH 15/20] [powerpc, netdevices] Constify & voidify get_property() Jeremy Kerr
2006-07-10 12:43 ` Paul Mackerras
2006-07-04 6:47 [PATCH 15/20] [powerpc,netdevices] " Jeremy Kerr
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=17582.14562.991790.920984@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=cbe-oss-dev@ozlabs.org \
--cc=jk@ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@oss.sgi.com \
/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).