LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v4] powerpc: Unify opcode definitions and support
Date: Wed, 11 Feb 2009 00:11:32 -0600	[thread overview]
Message-ID: <DECF9965-04E1-4897-8686-147625C5EE93@kernel.crashing.org> (raw)
In-Reply-To: <20090211114011.04f838d6.sfr@canb.auug.org.au>


On Feb 10, 2009, at 6:40 PM, Stephen Rothwell wrote:

> 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 ...

posted a new version that should fix this (added GPL license)

- k

  reply	other threads:[~2009-02-11  6:11 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
2009-02-11  6:11   ` Kumar Gala [this message]
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=DECF9965-04E1-4897-8686-147625C5EE93@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sfr@canb.auug.org.au \
    /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