From: Ladislav Michl <oss-lists@triops.cz>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Liang He <windhl@126.com>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: [PATCH v3 3/3] usb: dwc3: Add SPDX header and copyright
Date: Sun, 16 Jul 2023 16:11:53 +0200 [thread overview]
Message-ID: <ZLP6qXR3O3X654/n@lenoch> (raw)
In-Reply-To: <2023071550-exploring-freeload-ef90@gregkh>
On Sat, Jul 15, 2023 at 07:23:29AM +0200, Greg Kroah-Hartman wrote:
> On Fri, Jul 14, 2023 at 09:46:13PM +0000, Thinh Nguyen wrote:
> > On Fri, Jul 14, 2023, Ladislav Michl wrote:
> > > From: Ladislav Michl <ladis@linux-mips.org>
> > >
> > > As driver is rewritten and David no longer works for Marvell (Cavium),
> > > I'm to blame for breakage.
> > >
> > > Signed-off-by: Ladislav Michl <ladis@linux-mips.org>
> > > ---
> > > CHANGES:
> > > - v2: None
> > > - v3: None
> > >
> > > drivers/usb/dwc3/dwc3-octeon.c | 10 ++++------
> > > 1 file changed, 4 insertions(+), 6 deletions(-)
> > >
> > > diff --git a/drivers/usb/dwc3/dwc3-octeon.c b/drivers/usb/dwc3/dwc3-octeon.c
> > > index dd47498f4efb..a68d568b11a9 100644
> > > --- a/drivers/usb/dwc3/dwc3-octeon.c
> > > +++ b/drivers/usb/dwc3/dwc3-octeon.c
> > > @@ -1,11 +1,9 @@
> > > +// SPDX-License-Identifier: GPL-2.0
> > > /*
> > > - * XHCI HCD glue for Cavium Octeon III SOCs.
> > > + * DWC3 glue for Cavium Octeon III SOCs.
> > > *
> > > * Copyright (C) 2010-2017 Cavium Networks
> > > - *
> > > - * This file is subject to the terms and conditions of the GNU General Public
> > > - * License. See the file "COPYING" in the main directory of this archive
> > > - * for more details.
> > > + * Copyright (C) 2023 Ladislav Michl <ladis@linux-mips.org>
> >
> > I may not be an expert with Copyright, but is it correct to put your
> > name rather than the entity this belongs to?
>
> That is up to the employer of the developer as to what they want to see
> here. Ladislav, you have run this by your legal group, right?
Not this particular one as I do not have any legal group :) I started
this cleanup on my own, but it turned out there will be much more work
needed to make USB on Octeon reliable. So after asking my contact person
at Racom, copyright will be assigned to them. Note that it is not official
statement yet, but as Thinh is on holidays anyway, we have quite some
time to sort this out. I'll either confirm or send v5 - v4 is is on the
way with Thinh's comments addressed, so I'm lookign forward for feedback.
Thanks,
ladis
prev parent reply other threads:[~2023-07-16 14:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 7:37 [PATCH v3 0/3] Cleanup Octeon DWC3 glue code Ladislav Michl
2023-07-14 7:39 ` [PATCH v3 1/3] usb: dwc3: dwc3-octeon: Convert to glue driver Ladislav Michl
2023-07-14 21:44 ` Thinh Nguyen
2023-07-14 7:41 ` [PATCH v3 2/3] usb: dwc3: dwc3-octeon: Move node parsing into driver probe Ladislav Michl
2023-07-14 22:26 ` Thinh Nguyen
2023-07-14 7:41 ` [PATCH v3 3/3] usb: dwc3: Add SPDX header and copyright Ladislav Michl
2023-07-14 21:46 ` Thinh Nguyen
2023-07-15 5:23 ` Greg Kroah-Hartman
2023-07-16 14:11 ` Ladislav Michl [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=ZLP6qXR3O3X654/n@lenoch \
--to=oss-lists@triops.cz \
--cc=Thinh.Nguyen@synopsys.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
--cc=windhl@126.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).