From: Paul Mackerras <paulus@samba.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Mark Nelson <markn@au1.ibm.com>, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 1/2] powerpc: Add new CPU feature: CPU_FTR_UNALIGNED_LD_STD
Date: Tue, 28 Oct 2008 14:16:40 +1100 [thread overview]
Message-ID: <18694.33816.996886.431170@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <349712B7-EA3A-4BAA-9DB8-8A5FDD0AA060@kernel.crashing.org>
Kumar Gala writes:
> not that I have anything against this patch but is there anything we
> can do about the CPU_FTR_ usage for one of things like this?
<blinks>
Can you express that a little more coherently for us, please? :)
Paul.
next prev parent reply other threads:[~2008-10-28 3:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 10:43 [PATCH 1/2] powerpc: Add new CPU feature: CPU_FTR_UNALIGNED_LD_STD Mark Nelson
2008-10-27 13:44 ` Kumar Gala
2008-10-28 3:16 ` Paul Mackerras [this message]
2008-10-28 13:21 ` Kumar Gala
2008-10-28 22:05 ` Paul Mackerras
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=18694.33816.996886.431170@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=markn@au1.ibm.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).