[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zwmi-MEVE_E4nkzl@bombadil.infradead.org>
Date: Fri, 11 Oct 2024 15:13:12 -0700
From: Luis Chamberlain <mcgrof@...nel.org>
To: Matthew Maurer <mmaurer@...gle.com>
Cc: masahiroy@...nel.org, ndesaulniers@...gle.com, ojeda@...nel.org,
gary@...yguo.net, Alex Gaynor <alex.gaynor@...il.com>,
rust-for-linux@...r.kernel.org, linux-kbuild@...r.kernel.org,
linux-kernel@...r.kernel.org, neal@...pa.dev, marcan@...can.st,
j@...nau.net, asahi@...ts.linux.dev, linux-modules@...r.kernel.org,
Boqun Feng <boqun.feng@...il.com>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <benno.lossin@...ton.me>,
Andreas Hindborg <a.hindborg@...nel.org>,
Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>
Subject: Re: [PATCH v5 13/16] export_report: Rehabilitate script
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
Powered by blists - more mailing lists