From: Aaron Tomlin <atomlin@atomlin.com>
To: David Vernet <void@manifault.com>
Cc: Aaron Tomlin <atomlin@redhat.com>,
mcgrof@kernel.org, cl@linux.com, pmladek@suse.com,
mbenes@suse.cz, akpm@linux-foundation.org, jeyu@kernel.org,
linux-kernel@vger.kernel.org, linux-modules@vger.kernel.org,
ghalat@redhat.com, allen.lkml@gmail.com
Subject: Re: [RFC PATCH v2 03/13] module: Move livepatch support to a separate file
Date: Thu, 13 Jan 2022 10:35:31 +0000 [thread overview]
Message-ID: <20220113103531.sn76g34tfkxscs4e@ava.usersys.com> (raw)
In-Reply-To: <Yd8j/Q2H0zYrAA2c@dev0025.ash9.facebook.com>
On Wed 2022-01-12 10:54 -0800, David Vernet wrote:
> Thanks for doing this refactor. +1 to doing this, though Petr had some
> suggestions in another thread that I'll wait on before Acking.
No problem and yes, I will make the suggested modifications then add you on
Cc.
> Aaron Tomlin <atomlin@redhat.com> wrote on Thu [2022-Jan-06 23:43:09 +0000]:
> > diff --git a/kernel/module/livepatch.c b/kernel/module/livepatch.c
> > new file mode 100644
> > index 000000000000..e147f5418327
> > --- /dev/null
> > +++ b/kernel/module/livepatch.c
> > @@ -0,0 +1,75 @@
> > +// SPDX-License-Identifier: GPL-2.0-or-later
> > +/*
> > + * kernel/module/livepatch.c - module livepatch support
> > + *
> > + * Copyright (C) 2016 Jessica Yu <jeyu@redhat.com>
> > + */
>
> Should the copyright year (and possibly author) be updated? Or just removed
> entirely?
Who should I specify? I'm not entirely sure. If I understand correctly,
Jessica was the original author of the majority.
Kind regards,
--
Aaron Tomlin
next prev parent reply other threads:[~2022-01-13 10:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 23:43 [RFC PATCH v2 00/13] module: core code clean up Aaron Tomlin
2022-01-06 23:43 ` [RFC PATCH v2 01/13] module: Move all into module/ Aaron Tomlin
2022-01-06 23:43 ` [RFC PATCH v2 02/13] module: Simple refactor in preparation for split Aaron Tomlin
2022-01-06 23:43 ` [RFC PATCH v2 03/13] module: Move livepatch support to a separate file Aaron Tomlin
2022-01-12 16:53 ` Petr Mladek
2022-01-12 18:40 ` David Vernet
2022-01-14 9:14 ` Aaron Tomlin
2022-01-12 18:54 ` David Vernet
2022-01-13 10:35 ` Aaron Tomlin [this message]
2022-01-13 14:16 ` David Vernet
2022-01-13 15:12 ` Luis Chamberlain
2022-01-06 23:43 ` [RFC PATCH v2 04/13] module: Move latched RB-tree " Aaron Tomlin
2022-01-06 23:43 ` [RFC PATCH v2 05/13] module: Move arch strict rwx " Aaron Tomlin
2022-01-06 23:43 ` [RFC PATCH v2 06/13] module: Move " Aaron Tomlin
2022-01-06 23:43 ` [RFC PATCH v2 07/13] module: Move extra signature support out of core code Aaron Tomlin
2022-01-06 23:43 ` [RFC PATCH v2 08/13] module: Move kmemleak support to a separate file Aaron Tomlin
2022-01-06 23:43 ` [RFC PATCH v2 09/13] module: Move kallsyms support into " Aaron Tomlin
2022-01-06 23:43 ` [RFC PATCH v2 10/13] module: Move procfs " Aaron Tomlin
2022-01-06 23:43 ` [RFC PATCH v2 11/13] module: Move sysfs " Aaron Tomlin
2022-01-06 23:43 ` [RFC PATCH v2 12/13] module: Move kdb_modules list out of core code Aaron Tomlin
2022-01-11 14:55 ` [RFC PATCH v2 00/13] module: core code clean up Allen
2022-01-12 1:16 ` Allen
2022-01-12 13:21 ` Aaron Tomlin
2022-01-12 15:52 ` Luis Chamberlain
2022-01-13 9:23 ` Aaron Tomlin
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=20220113103531.sn76g34tfkxscs4e@ava.usersys.com \
--to=atomlin@atomlin.com \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=atomlin@redhat.com \
--cc=cl@linux.com \
--cc=ghalat@redhat.com \
--cc=jeyu@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mcgrof@kernel.org \
--cc=pmladek@suse.com \
--cc=void@manifault.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).