From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v4] powerpc: Unify opcode definitions and support
Date: Wed, 11 Feb 2009 11:40:11 +1100 [thread overview]
Message-ID: <20090211114011.04f838d6.sfr@canb.auug.org.au> (raw)
In-Reply-To: <1234312110-22227-1-git-send-email-galak@kernel.crashing.org>
[-- Attachment #1: Type: text/plain, Size: 472 bytes --]
Hi Kumar,
On Tue, 10 Feb 2009 18:28:30 -0600 Kumar Gala <galak@kernel.crashing.org> wrote:
>
> +++ b/arch/powerpc/include/asm/ppc-opcode.h
> @@ -0,0 +1,68 @@
> +/*
> + * Copyright (C) 2009 Freescale Semicondutor, Inc. All rights reserved.
If you are going to use "All rights reserved", you should also allow us
to use it under the GPL explicitly ...
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-02-11 0:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 0:28 [PATCH v4] powerpc: Unify opcode definitions and support Kumar Gala
2009-02-11 0:40 ` Stephen Rothwell [this message]
2009-02-11 6:11 ` Kumar Gala
2009-02-11 6:53 ` Stephen Rothwell
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=20090211114011.04f838d6.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=galak@kernel.crashing.org \
--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