From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Pengbo Mu <pengbo.mu@nxp.com>
Cc: Felipe Balbi <balbi@kernel.org>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb: phy: fix copyright issue of phy-fsl-usb.c
Date: Tue, 17 Jul 2018 09:19:50 +0200 [thread overview]
Message-ID: <20180717071950.GA12255@kroah.com> (raw)
In-Reply-To: <1531811402-44183-1-git-send-email-pengbo.mu@nxp.com>
On Tue, Jul 17, 2018 at 03:10:02PM +0800, Pengbo Mu wrote:
> Fixed the copyright issue of drivers/usb/phy/phy-fsl-usb.c.
I still fail to understand what exactly the "copyright issue" is here.
Can you provide some details please.
Ideally you would have your lawyer sign off on this patch, as they know
this type of law better than we do :)
thanks,
greg k-h
next prev parent reply other threads:[~2018-07-17 7:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 7:10 [PATCH] usb: phy: fix copyright issue of phy-fsl-usb.c Pengbo Mu
2018-07-17 7:11 ` Felipe Balbi
2018-07-17 7:19 ` Greg Kroah-Hartman [this message]
2018-07-17 16:36 ` Joe Perches
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=20180717071950.GA12255@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=balbi@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pengbo.mu@nxp.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).