From: Greg KH <gregkh@linuxfoundation.org>
To: Tanzir Hasan <tanzirh@google.com>
Cc: Kees Cook <keescook@chromium.org>,
Nick DeSaulniers <nnn@google.com>,
Andy Shevchenko <andy@kernel.org>,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
llvm@lists.linux.dev, Al Viro <viro@zeniv.linux.org.uk>,
Andy Shevchenko <andy.shevchenko@gmail.com>
Subject: Re: [PATCH v4 1/2] kernel.h: removed REPEAT_BYTE from kernel.h
Date: Tue, 19 Dec 2023 20:10:53 +0100 [thread overview]
Message-ID: <2023121928-propose-florist-5898@gregkh> (raw)
In-Reply-To: <CAE-cH4p-TzH3zyJfmSg3r=fw78j8y-0t0dp-NvaLyVYAMULw1w@mail.gmail.com>
On Tue, Dec 19, 2023 at 10:35:55AM -0800, Tanzir Hasan wrote:
> > Legal note, this file is NOT copyright Google as no Google employe
> > actually wrote the logcal contents of it.
> >
> > Please be VERY careful when doing stuff like this, it has potentially
> > big repercussions, and you don't want to have to talk to lots of
> > lawyers a few years from now and explain how you messed it all up :(
>
> Ah, sorry, I didn't realize. Will change right away.
>
> > Nick, odds are there's a Google copyright class that Tanzir should take
> > here, if not, I recommend the free LF one that anyone can take online
> > that explains the issues here:
> > https://training.linuxfoundation.org/training/open-source-licensing-basics-for-software-developers/
>
> I will take a look, thanks!
Please take the time to either learn what the Google-specific rules are,
or take the above training, before submitting a new version of the
patch.
thanks,
greg k-h
next prev parent reply other threads:[~2023-12-19 19:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 18:09 [PATCH v4 0/2] shrink lib/string.i via IWYU Tanzir Hasan
2023-12-19 18:09 ` [PATCH v4 1/2] kernel.h: removed REPEAT_BYTE from kernel.h Tanzir Hasan
2023-12-19 18:22 ` Greg KH
2023-12-19 18:35 ` Tanzir Hasan
2023-12-19 19:10 ` Greg KH [this message]
2023-12-19 23:00 ` Nick Desaulniers
2023-12-20 6:03 ` Greg KH
2023-12-19 21:47 ` Andy Shevchenko
2023-12-19 18:09 ` [PATCH v4 2/2] lib/string: shrink lib/string.i via IWYU Tanzir Hasan
2023-12-19 18:24 ` Greg KH
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=2023121928-propose-florist-5898@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nnn@google.com \
--cc=tanzirh@google.com \
--cc=viro@zeniv.linux.org.uk \
/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