linux-modules.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Alcock <nick.alcock@oracle.com>
To: Nick Alcock <nick.alcock@oracle.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Luis Chamberlain <mcgrof@kernel.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Christoph Hellwig <hch@infradead.org>,
	linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org,
	Hitomi Hasegawa <hasegawa-hitomi@fujitsu.com>,
	Jiri Slaby <jirislaby@kernel.org>
Subject: Re: [PATCH 10/17] tty: remove MODULE_LICENSE in non-modules
Date: Mon, 27 Mar 2023 19:23:53 +0100	[thread overview]
Message-ID: <87wn32m4sm.fsf@esperi.org.uk> (raw)
In-Reply-To: <87355qnt27.fsf@esperi.org.uk> (Nick Alcock's message of "Mon, 27 Mar 2023 15:54:24 +0100")

On 27 Mar 2023, Nick Alcock uttered the following:
> Well, it seems to me that you're really objecting to the consequences of
> a years-old commit that I didn't write. Since the person who did write
> it seems to hate me for unclear reasons,

I should probably apologise: this was uncalled for. Stressful day and I
typed without thinking (and then rephrased it repeatedly without
thinking). So, sorry! Mea culpa etc.

(I am *good* at putting both feet in it)

  reply	other threads:[~2023-03-27 18:32 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-02 21:17 [PATCH 00/17] MODULE_LICENSE removals, sixth tranche Nick Alcock
2023-03-02 21:17 ` [PATCH 01/17] irqchip: remove MODULE_LICENSE in non-modules Nick Alcock
2023-03-02 21:17 ` [PATCH 02/17] bus: " Nick Alcock
2023-03-02 21:17 ` [PATCH 03/17] braille_console: " Nick Alcock
2023-03-02 21:17 ` [PATCH 04/17] arm-cci: " Nick Alcock
2023-03-02 21:17 ` [PATCH 05/17] drivers: bus: simple-pm-bus: " Nick Alcock
2023-03-03  7:52   ` Geert Uytterhoeven
2023-03-03 18:32     ` Nick Alcock
2023-03-03 18:43       ` Geert Uytterhoeven
2023-03-20 10:58     ` Nick Alcock
2023-03-02 21:17 ` [PATCH 06/17] watch_queue: " Nick Alcock
2023-03-02 21:17 ` [PATCH 07/17] btree: " Nick Alcock
2023-03-02 21:17 ` [PATCH 08/17] lib: " Nick Alcock
2023-03-02 21:17 ` [PATCH 09/17] fprobe: " Nick Alcock
2023-03-02 21:17 ` [PATCH 10/17] tty: " Nick Alcock
2023-03-09 16:15   ` Greg Kroah-Hartman
2023-03-09 22:38     ` Luis Chamberlain
2023-03-10  7:31       ` Greg Kroah-Hartman
2023-03-10 19:33         ` Luis Chamberlain
2023-03-24  9:08           ` Geert Uytterhoeven
2023-03-24  9:12             ` Geert Uytterhoeven
2023-03-24  9:14             ` Greg Kroah-Hartman
2023-03-24  9:16               ` Geert Uytterhoeven
2023-03-24 14:16                 ` Nick Alcock
2023-03-24 14:29                   ` Greg Kroah-Hartman
2023-03-24 18:06                     ` Luis Chamberlain
2023-03-27 10:46                       ` Nick Alcock
2023-03-27 11:43                         ` Greg Kroah-Hartman
2023-03-27 14:54                           ` Nick Alcock
2023-03-27 18:23                             ` Nick Alcock [this message]
2023-03-29  2:50                               ` Luis Chamberlain
2023-04-13 20:24                       ` Luis Chamberlain
2023-03-26  4:52               ` Christoph Hellwig
2023-03-02 21:17 ` [PATCH 11/17] unicode: " Nick Alcock
2023-03-06 15:32   ` Gabriel Krisman Bertazi
2023-03-02 21:17 ` [PATCH 12/17] udmabuf: " Nick Alcock
2023-03-02 21:17 ` [PATCH 13/17] regulator: stm32-pwr: " Nick Alcock
2023-03-03  0:31   ` Mark Brown
2023-03-03 18:30     ` Nick Alcock
2023-03-04 20:12       ` Mark Brown
2023-03-02 21:17 ` [PATCH 14/17] mm: " Nick Alcock
2023-03-02 21:17 ` [PATCH 15/17] xen: " Nick Alcock
2023-03-06  7:45   ` Juergen Gross
2023-03-02 21:17 ` [PATCH 16/17] zpool: " Nick Alcock
2023-03-02 21:17 ` [PATCH 17/17] zswap: " Nick Alcock
2023-03-03 22:22 ` [PATCH 00/17] MODULE_LICENSE removals, sixth tranche Luis Chamberlain
2023-03-20 11:00   ` Nick Alcock

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=87wn32m4sm.fsf@esperi.org.uk \
    --to=nick.alcock@oracle.com \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hasegawa-hitomi@fujitsu.com \
    --cc=hch@infradead.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=tglx@linutronix.de \
    /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).