From: Luis Chamberlain <mcgrof@kernel.org>
To: Matthew Maurer <mmaurer@google.com>
Cc: masahiroy@kernel.org, ndesaulniers@google.com, ojeda@kernel.org,
gary@garyguo.net, "Alex Gaynor" <alex.gaynor@gmail.com>,
rust-for-linux@vger.kernel.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, neal@gompa.dev, marcan@marcan.st,
j@jannau.net, asahi@lists.linux.dev,
linux-modules@vger.kernel.org,
"Boqun Feng" <boqun.feng@gmail.com>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>
Subject: Re: [PATCH v5 13/16] export_report: Rehabilitate script
Date: Fri, 11 Oct 2024 15:13:12 -0700 [thread overview]
Message-ID: <Zwmi-MEVE_E4nkzl@bombadil.infradead.org> (raw)
In-Reply-To: <20240925233854.90072-14-mmaurer@google.com>
On Wed, Sep 25, 2024 at 11:38:28PM +0000, Matthew Maurer wrote:
> * modules.order has .o files when in a build dir, support this
The commit log is not clear, is it that it's always had *.o files, and
you're adding them now, why? Why is the .ko search now removed?
> * .mod.c source layout has changed,
When, why did this change not happen at that time?
> update regexes to match
Why did this not break anything before ? Is this fixing something, or
is it prep work?
> * Add a stage 3, to be more robust against additional .mod.c content
Future .mod.c changes?
Luis
next prev parent reply other threads:[~2024-10-11 22:13 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 23:38 [PATCH v5 00/16] Extended MODVERSIONS Support Matthew Maurer
2024-09-25 23:38 ` [PATCH v5 01/16] module: Take const arg in validate_section_offset Matthew Maurer
2024-09-25 23:38 ` [PATCH v5 02/16] module: Factor out elf_validity_ehdr Matthew Maurer
2024-09-25 23:38 ` [PATCH v5 03/16] module: Factor out elf_validity_cache_sechdrs Matthew Maurer
2024-09-25 23:38 ` [PATCH v5 04/16] module: Factor out elf_validity_cache_secstrings Matthew Maurer
2024-09-25 23:38 ` [PATCH v5 05/16] module: Factor out elf_validity_cache_index_info Matthew Maurer
2024-09-25 23:38 ` [PATCH v5 06/16] module: Factor out elf_validity_cache_index_mod Matthew Maurer
2024-09-25 23:38 ` [PATCH v5 07/16] module: Factor out elf_validity_cache_index_sym Matthew Maurer
2024-09-25 23:38 ` [PATCH v5 08/16] module: Factor out elf_validity_cache_index_str Matthew Maurer
2024-09-25 23:38 ` [PATCH v5 09/16] module: Group section index calculations together Matthew Maurer
2024-09-25 23:38 ` [PATCH v5 10/16] module: Factor out elf_validity_cache_strtab Matthew Maurer
2024-09-25 23:38 ` [PATCH v5 11/16] module: Additional validation in elf_validity_cache_strtab Matthew Maurer
2024-09-25 23:38 ` [PATCH v5 12/16] module: Reformat struct for code style Matthew Maurer
2024-09-25 23:38 ` [PATCH v5 13/16] export_report: Rehabilitate script Matthew Maurer
2024-10-11 22:13 ` Luis Chamberlain [this message]
2024-10-11 22:22 ` Matthew Maurer
2024-10-11 22:29 ` Luis Chamberlain
2024-09-25 23:38 ` [PATCH v5 14/16] modules: Support extended MODVERSIONS info Matthew Maurer
2024-09-26 12:22 ` Christophe Leroy
2024-09-26 18:36 ` Sami Tolvanen
2024-10-11 22:22 ` Luis Chamberlain
2024-10-11 22:27 ` Matthew Maurer
2024-10-11 22:33 ` Luis Chamberlain
2024-10-11 23:45 ` Luis Chamberlain
2024-10-11 23:46 ` Luis Chamberlain
2024-10-15 23:22 ` Matthew Maurer
2024-10-16 23:21 ` Luis Chamberlain
2024-10-17 4:41 ` Christophe Leroy
2024-10-17 12:08 ` Helge Deller
2024-10-19 20:45 ` Luis Chamberlain
2024-10-21 19:35 ` Luis Chamberlain
2024-09-25 23:38 ` [PATCH v5 15/16] modpost: Produce extended modversion information Matthew Maurer
2024-09-25 23:38 ` [PATCH v5 16/16] export_report: Use new version info format Matthew Maurer
2024-09-26 22:53 ` [PATCH v5 00/16] Extended MODVERSIONS Support Sami Tolvanen
2024-09-28 21:35 ` Neal Gompa
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=Zwmi-MEVE_E4nkzl@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=asahi@lists.linux.dev \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=j@jannau.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=masahiroy@kernel.org \
--cc=mmaurer@google.com \
--cc=ndesaulniers@google.com \
--cc=neal@gompa.dev \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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).