From: Thomas Gleixner <tglx@linutronix.de>
To: Eddie James <eajames@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-hwmon@vger.kernel.org,
linux@roeck-us.net, joel@jms.id.au, jdelvare@suse.com,
Eddie James <eajames@linux.vnet.ibm.com>
Subject: Re: [PATCH v2 0/2] occ: FSI and hwmon: Fix license headers
Date: Tue, 29 Jan 2019 09:53:22 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.21.1901290953020.1669@nanos.tec.linutronix.de> (raw)
In-Reply-To: <1548692604-9899-1-git-send-email-eajames@linux.ibm.com>
On Mon, 28 Jan 2019, Eddie James wrote:
> From: Eddie James <eajames@linux.vnet.ibm.com>
>
> Source files for the FSI OCC and OCC hwmon drivers had a combination of bad
> license information and missing IBM copyright. Correct the licenses.
Thanks for cleaning that up!
tglx
prev parent reply other threads:[~2019-01-29 8:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 16:23 [PATCH v2 0/2] occ: FSI and hwmon: Fix license headers Eddie James
2019-01-28 16:23 ` [PATCH v2 1/2] hwmon (occ): " Eddie James
2019-01-31 17:58 ` Guenter Roeck
2019-01-28 16:23 ` [PATCH v2 2/2] fsi: occ: Fix license header Eddie James
2019-01-29 8:53 ` Thomas Gleixner [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=alpine.DEB.2.21.1901290953020.1669@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=eajames@linux.ibm.com \
--cc=eajames@linux.vnet.ibm.com \
--cc=jdelvare@suse.com \
--cc=joel@jms.id.au \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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).