From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Alex Courbot <acourbot@nvidia.com>
Cc: Len Brown <lenb@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
David Cohen <david.a.cohen@linux.intel.com>,
Sathyanarayanan Kuppuswamy <sathyanarayanan.kuppuswamy@intel.com>
Subject: Re: [PATCH] SFI: remove wrong FSF address from the license
Date: Mon, 09 Dec 2013 11:52:10 +0200 [thread overview]
Message-ID: <1386582730.1871.109.camel@smile> (raw)
In-Reply-To: <52A590CC.4040703@nvidia.com>
On Mon, 2013-12-09 at 18:43 +0900, Alex Courbot wrote:
> On 12/09/2013 06:32 PM, Andy Shevchenko wrote:
> > Remove old and currently wrong address of the FSF from license parts of the
> > code.
>
> The address is not wrong, it is just that you don't want to see it
> become wrong should it change in the future.
Oh, I have misread that.
So, this patch probably is not needed at all.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
prev parent reply other threads:[~2013-12-09 9:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 9:32 [PATCH] SFI: remove wrong FSF address from the license Andy Shevchenko
2013-12-09 9:43 ` Alex Courbot
2013-12-09 9:52 ` Andy Shevchenko [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=1386582730.1871.109.camel@smile \
--to=andriy.shevchenko@linux.intel.com \
--cc=acourbot@nvidia.com \
--cc=david.a.cohen@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sathyanarayanan.kuppuswamy@intel.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