From: Nick Alcock <nick.alcock@oracle.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Nick Alcock <nick.alcock@oracle.com>,
mcgrof@kernel.org, linux-clk@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-modules@vger.kernel.org, linux-perf-users@vger.kernel.org,
linux-pm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
linux-riscv@lists.infradead.org, linux-serial@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-trace-devel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH 00/20] MODULE_LICENSE removals, fifth tranche
Date: Mon, 20 Mar 2023 11:06:45 +0000 [thread overview]
Message-ID: <87bkknu1fe.fsf@esperi.org.uk> (raw)
In-Reply-To: <CAMuHMdUo3BkELZzhr0yVF7eU53_h757m1QWN8fQeLWKe5fCZDA@mail.gmail.com> (Geert Uytterhoeven's message of "Tue, 28 Feb 2023 14:47:48 +0100")
On 28 Feb 2023, Geert Uytterhoeven outgrape:
> On Tue, Feb 28, 2023 at 2:05 PM Nick Alcock <nick.alcock@oracle.com> wrote:
>> This series, based on current modules-next, is part of a treewide cleanup
>> suggested by Luis Chamberlain, to remove the LICENSE_MODULE usage from
>> files/objects that are not tristate. Due to recent changes to kbuild, these
>> uses are now problematic. See the commit logs for more details.
>
> Does this mean you expect us to queue them for v6.3?
> Thanks!
I believe Luis is planning to pull them in around -rc3, hence my
freshening the series up now, getting everyone's tags in, etc.
--
NULL && (void)
WARNING: multiple messages have this Message-ID (diff)
From: Nick Alcock <nick.alcock@oracle.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Nick Alcock <nick.alcock@oracle.com>,
mcgrof@kernel.org, linux-clk@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-modules@vger.kernel.org, linux-perf-users@vger.kernel.org,
linux-pm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
linux-riscv@lists.infradead.org, linux-serial@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-trace-devel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH 00/20] MODULE_LICENSE removals, fifth tranche
Date: Mon, 20 Mar 2023 11:06:45 +0000 [thread overview]
Message-ID: <87bkknu1fe.fsf@esperi.org.uk> (raw)
In-Reply-To: <CAMuHMdUo3BkELZzhr0yVF7eU53_h757m1QWN8fQeLWKe5fCZDA@mail.gmail.com> (Geert Uytterhoeven's message of "Tue, 28 Feb 2023 14:47:48 +0100")
On 28 Feb 2023, Geert Uytterhoeven outgrape:
> On Tue, Feb 28, 2023 at 2:05 PM Nick Alcock <nick.alcock@oracle.com> wrote:
>> This series, based on current modules-next, is part of a treewide cleanup
>> suggested by Luis Chamberlain, to remove the LICENSE_MODULE usage from
>> files/objects that are not tristate. Due to recent changes to kbuild, these
>> uses are now problematic. See the commit logs for more details.
>
> Does this mean you expect us to queue them for v6.3?
> Thanks!
I believe Luis is planning to pull them in around -rc3, hence my
freshening the series up now, getting everyone's tags in, etc.
--
NULL && (void)
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-03-20 11:11 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 13:01 [PATCH 00/20] MODULE_LICENSE removals, fifth tranche Nick Alcock
2023-02-28 13:01 ` Nick Alcock
2023-02-28 13:01 ` [PATCH 01/20] perf/hw_breakpoint: remove MODULE_LICENSE in non-modules Nick Alcock
2023-02-28 13:01 ` [PATCH 02/20] pinctrl: amd: " Nick Alcock
2023-03-07 13:08 ` Linus Walleij
2023-02-28 13:01 ` [PATCH 03/20] pinctrl: mediatek: " Nick Alcock
2023-02-28 13:01 ` Nick Alcock
2023-02-28 13:01 ` [PATCH 04/20] pinctrl: renesas: " Nick Alcock
2023-02-28 13:02 ` [PATCH 05/20] lib: " Nick Alcock
2023-02-28 16:35 ` Keller, Jacob E
2023-02-28 13:02 ` [PATCH 06/20] powercap: " Nick Alcock
2023-02-28 20:33 ` Rafael J. Wysocki
2023-02-28 13:02 ` [PATCH 07/20] power: supply: " Nick Alcock
2023-02-28 13:02 ` [PATCH 08/20] remoteproc: " Nick Alcock
2023-02-28 13:35 ` Mukesh Ojha
2023-03-02 22:01 ` Mathieu Poirier
2023-02-28 13:02 ` [PATCH 09/20] clk: renesas: " Nick Alcock
2023-02-28 13:45 ` Geert Uytterhoeven
2023-02-28 14:07 ` Adam Ford
2023-03-20 11:08 ` Nick Alcock
2023-02-28 13:02 ` [PATCH 10/20] reset: mchp: sparx5: " Nick Alcock
2023-02-28 13:02 ` Nick Alcock
2023-02-28 14:53 ` Steen Hegelund
2023-02-28 14:53 ` Steen Hegelund
2023-02-28 13:02 ` [PATCH 11/20] reset: lantiq: " Nick Alcock
2023-02-28 13:02 ` [PATCH 12/20] clk: microchip: mpfs: " Nick Alcock
2023-02-28 13:02 ` Nick Alcock
2023-02-28 19:19 ` Conor Dooley
2023-02-28 19:19 ` Conor Dooley
2023-02-28 13:02 ` [PATCH 13/20] reset: " Nick Alcock
2023-02-28 13:02 ` Nick Alcock
2023-02-28 19:17 ` Conor Dooley
2023-02-28 19:17 ` Conor Dooley
2023-02-28 19:26 ` Nick Alcock
2023-02-28 19:26 ` Nick Alcock
2023-02-28 19:53 ` Conor Dooley
2023-02-28 19:53 ` Conor Dooley
2023-02-28 13:02 ` [PATCH 14/20] rv/reactor: " Nick Alcock
2023-02-28 13:19 ` Daniel Bristot de Oliveira
2023-02-28 13:02 ` [PATCH 15/20] tty: serial: imx: " Nick Alcock
2023-02-28 13:02 ` Nick Alcock
2023-02-28 13:02 ` [PATCH 16/20] irqchip/irq-sl28cpld: " Nick Alcock
2023-02-28 16:12 ` Michael Walle
2023-02-28 13:02 ` [PATCH 17/20] ARC: reset: " Nick Alcock
2023-02-28 13:02 ` [PATCH 18/20] " Nick Alcock
2023-02-28 13:02 ` [PATCH 19/20] power: " Nick Alcock
2023-02-28 13:02 ` [PATCH 20/20] soc/tegra: cbb: " Nick Alcock
2023-04-05 13:09 ` (subset) " Thierry Reding
2023-02-28 13:47 ` [PATCH 00/20] MODULE_LICENSE removals, fifth tranche Geert Uytterhoeven
2023-02-28 13:47 ` Geert Uytterhoeven
2023-03-20 11:06 ` Nick Alcock [this message]
2023-03-20 11:06 ` Nick Alcock
2023-03-09 16:14 ` Greg KH
2023-03-09 16:14 ` 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=87bkknu1fe.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--cc=geert@linux-m68k.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mcgrof@kernel.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.