From: Greg KH <greg@kroah.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] [PATCH 5/5] staging:lustre: Update license and copyright for kernel comm
Date: Thu, 29 Oct 2015 07:45:13 +0900 [thread overview]
Message-ID: <20151028224513.GA31326@kroah.com> (raw)
In-Reply-To: <ef7c51eacffd4e9880cd39c0ede13348@EXCHCS32.ornl.gov>
On Wed, Oct 28, 2015 at 07:00:29PM +0000, Simmons, James A. wrote:
> >>
> >> - * http://www.sun.com/software/products/lustre/docs/GPLv2.pdf
> >> - *
> >> - * Please contact Sun Microsystems, Inc., 4150 Network Circle, Santa Clara,
> >> - * CA 95054 USA or visit www.sun.com if you need additional information or
> >> - * have any questions.
> >
> >That text is in every files. You should kill all references.
>
> That would be a mighty big patch.
I can take "mighty big patches" like this quite easily, please send it
to me, don't mess with this "development branch of an external tree"
nonsense, which I'm _REALLY_ getting tired of.
Please drop that tree and only use the in-kernel version. If that
doesn't work for you, then we need to drop the in-kernel version as it's
pretty obvious no one is actually using this in-kernel code.
thanks,
greg k-h
next prev parent reply other threads:[~2015-10-28 22:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 10:49 [lustre-devel] [PATCH 5/5] staging:lustre: Update license and copyright for kernel comm Xose Vazquez Perez
2015-10-28 19:00 ` Simmons, James A.
2015-10-28 22:45 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-10-23 19:59 [lustre-devel] [PATCH 0/5] staging:lustre: split kernel comm between user and kernel James Simmons
2015-10-23 19:59 ` [lustre-devel] [PATCH 5/5] staging:lustre: Update license and copyright for kernel comm James Simmons
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=20151028224513.GA31326@kroah.com \
--to=greg@kroah.com \
--cc=lustre-devel@lists.lustre.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.