From: Nick Alcock <nick.alcock@oracle.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: mcgrof@kernel.org, linux-modules@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/7] MODULE_LICENSE removals, first tranche
Date: Thu, 16 Feb 2023 19:20:56 +0000 [thread overview]
Message-ID: <87edqpv2lj.fsf@esperi.org.uk> (raw)
In-Reply-To: <20230216174333.GA3313434@bhelgaas> (Bjorn Helgaas's message of "Thu, 16 Feb 2023 11:43:33 -0600")
[Cc: slashed]
On 16 Feb 2023, Bjorn Helgaas said:
> [+cc PCI folks, who got the patches but not this cover letter, and
> participants from the v1 posting]
Oh I'm sorry! I think I need to arrange to augment the cover letter with
Cc:s too, to add all the mailing lists to it. This is extra-hard if (as
here) I'm splitting up the original patch series into pieces...
... or just try to do without a cover letter, and put all the stuff
which should be in the cover letter into the bit after the commit log
text. That might be simpler, since I could just stuff it unconditionally
into every mail without alteration.
--
NULL && (void)
prev parent reply other threads:[~2023-02-16 19:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 15:24 [PATCH v2 0/7] MODULE_LICENSE removals, first tranche Nick Alcock
2023-02-16 15:24 ` [PATCH v2 1/7] kbuild, PCI: versatile: remove MODULE_LICENSE in non-modules Nick Alcock
2023-02-16 15:24 ` [PATCH v2 2/7] kbuild, PCI: mobiveil: " Nick Alcock
2023-02-16 15:24 ` [PATCH v2 3/7] kbuild, PCI: tegra: " Nick Alcock
2023-02-16 15:24 ` [PATCH v2 4/7] kbuild, PCI: endpoint: " Nick Alcock
2023-02-16 18:11 ` Manivannan Sadhasivam
2023-02-16 15:24 ` [PATCH v2 5/7] kbuild, PCI: hip: " Nick Alcock
2023-02-16 15:24 ` [PATCH v2 6/7] kbuild, shpchp: " Nick Alcock
2023-02-16 15:24 ` [PATCH v2 7/7] kbuild, PCI: dwc: " Nick Alcock
2023-02-16 17:43 ` [PATCH v2 0/7] MODULE_LICENSE removals, first tranche Bjorn Helgaas
2023-02-16 18:01 ` Conor Dooley
2023-02-16 19:16 ` Bjorn Helgaas
2023-02-16 23:38 ` Conor Dooley
2023-02-16 19:20 ` Nick Alcock [this message]
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=87edqpv2lj.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@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 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).