From: "John W. Linville" <linville@tuxdriver.com>
To: Christian Lamparter <chunkeey@web.de>
Cc: linux-wireless@vger.kernel.org, Kalle Valo <kalle.valo@nokia.com>,
Larry Finger <Larry.Finger@lwfinger.net>,
Johannes Berg <johannes@sipsolutions.net>,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
tim.dewaal@yahoo.com
Subject: Re: [RFC][PATCH 5/5] p54: integrate parts of lmac_longbow.h and stlc45xx
Date: Mon, 6 Oct 2008 14:30:13 -0400 [thread overview]
Message-ID: <20081006183013.GC3448@tuxdriver.com> (raw)
In-Reply-To: <200810050239.44845.chunkeey@web.de>
On Sun, Oct 05, 2008 at 02:39:44AM +0200, Christian Lamparter wrote:
> This patch removes most/all? of the "magic" numbers and unknown structure
> variables inside the code and replaces them with meaningful prototypes.
> Therefore this patch got quite big.
>
> However, I'm not really sure what "(C)" I should put in and where exactly.
> But I hope ST's/Nokia's Legal Department or someone else who understands the
> laws good enough can give us a green light.
Why wouldn't it be "Copyright (C) 2007 Conexant Systems, Inc." as
from lmac_longbow.h, if anything at all? Or did you actually take
bits from stlc45xx? Even then I'm not sure specific attribution is
necessary for a few structure/variable/function names.
John
--
John W. Linville Linux should be at the core
linville@tuxdriver.com of your literate lifestyle.
prev parent reply other threads:[~2008-10-06 18:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-05 0:39 [RFC][PATCH 5/5] p54: integrate parts of lmac_longbow.h and stlc45xx Christian Lamparter
2008-10-06 18:30 ` John W. Linville [this message]
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=20081006183013.GC3448@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Larry.Finger@lwfinger.net \
--cc=chunkeey@web.de \
--cc=johannes@sipsolutions.net \
--cc=kalle.valo@nokia.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=tim.dewaal@yahoo.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).