Rust for Linux List
 help / color / mirror / Atom feed
From: Laura Abbott <laura@labbott.name>
To: Matthew Maurer <mmaurer@google.com>, Trevor Gross <tmgross@umich.edu>
Cc: gary@garyguo.net, masahiroy@kernel.org,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Alex Gaynor" <alex.gaynor@gmail.com>,
	"Wedson Almeida Filho" <wedsonaf@gmail.com>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <benno.lossin@proton.me>,
	"Andreas Hindborg" <a.hindborg@samsung.com>,
	"Alice Ryhl" <aliceryhl@google.com>,
	rust-for-linux@vger.kernel.org
Subject: Re: [PATCH 0/3] MODVERSIONS + RUST Redux
Date: Thu, 16 Nov 2023 09:49:58 -0500	[thread overview]
Message-ID: <970ee9d7-7e24-2376-a9cf-bfdf80385a0f@labbott.name> (raw)
In-Reply-To: <CAGSQo03pseM9ypkOZuX4UrHN=6kdBRq6a1sGH-T_T6WrOFgXzg@mail.gmail.com>

On 11/15/23 16:24, Matthew Maurer wrote:
> Should I be sending all these patches to all the lists? I was trying
> to follow the recommendations of get_maintainers.pl, which thought
> modules were the only relevant folks for the export_modules patches.
> (I also added Gary + Masahiro explicitly due to their involvement with
> the previous approach.)
> 
> If I should be sending all the patches to all the lists, should I also
> be adding all the suggested To/Cc lines for all the patches, or? I
> didn't see any suggestions on how to approach this in
> https://docs.kernel.org/process/submitting-patches.html#select-the-recipients-for-your-patch
> 


 From my experience doing work that touched a large number of areas
across the kernel, I would usually cc everyone on the cover letter
so they have context and then only add the relevant people/lists
to the specific patches. I would generate the patches then
manually go through and adjust the To/Cc lists from get_maintainers
before sending them out with git-send-email. Here, I would
definitely make sure the cover letter got sent to the powerpc
list for example.

That said, a three patch series is pretty short so you could
probably get away with ccing everyone on all the patches unless
you've gotten complaints. There are probably other opinions here
too.

Thanks,
Laura

      parent reply	other threads:[~2023-11-16 14:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-15 18:50 [PATCH 0/3] MODVERSIONS + RUST Redux Matthew Maurer
2023-11-15 18:50 ` [PATCH 2/3] modpost: Extended modversion support Matthew Maurer
2023-11-16 17:12   ` Luis Chamberlain
2023-11-15 21:05 ` [PATCH 0/3] MODVERSIONS + RUST Redux Trevor Gross
     [not found]   ` <CAGSQo01pE=V+NCdgp-1r_PAfn_48D4yXb91spHf8cZA0Z7GoLA@mail.gmail.com>
2023-11-15 21:24     ` Matthew Maurer
2023-11-15 21:54       ` Trevor Gross
2023-11-16  7:19         ` Ariel Miculas
2023-11-16 14:49       ` Laura Abbott [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=970ee9d7-7e24-2376-a9cf-bfdf80385a0f@labbott.name \
    --to=laura@labbott.name \
    --cc=a.hindborg@samsung.com \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=benno.lossin@proton.me \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=gary@garyguo.net \
    --cc=masahiroy@kernel.org \
    --cc=mmaurer@google.com \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tmgross@umich.edu \
    --cc=wedsonaf@gmail.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