linux-modules.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masahiro Yamada <masahiroy@kernel.org>
To: Matthew Maurer <mmaurer@google.com>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
	linux-kernel@vger.kernel.org,  linux-kbuild@vger.kernel.org,
	linux-modules@vger.kernel.org,
	 Sami Tolvanen <samitolvanen@google.com>
Subject: Re: [PATCH] scripts: Remove export_report.pl
Date: Wed, 30 Oct 2024 09:02:46 +0100	[thread overview]
Message-ID: <CAK7LNATYQAfsvU+Gm8FqBkKV-EMgHWD8Fp_mVrR5Uq81Lv5nEw@mail.gmail.com> (raw)
In-Reply-To: <20241029-remove-export-report-pl-v1-1-9cd6ccf93493@google.com>

On Tue, Oct 29, 2024 at 10:12 PM Matthew Maurer <mmaurer@google.com> wrote:
>
> This script has been broken for 5 years with no user complaints.
>
> It first had its .mod.c parser broken in commit a3d0cb04f7df ("modpost:
> use __section in the output to *.mod.c"). Later, it had its object file
> enumeration broken in commit f65a486821cf ("kbuild: change module.order
> to list *.o instead of *.ko"). Both of these changes sat for years with
> no reports.
>
> Rather than reviving this script as we make further changes to `.mod.c`,
> this patch gets rid of it because it is clearly unused.
>
> Signed-off-by: Matthew Maurer <mmaurer@google.com>
> ---
>  scripts/export_report.pl | 186 -----------------------------------------------
>  1 file changed, 186 deletions(-)


The top-level Makefile should be cleaned up.

$ git grep export_report -- Makefile
Makefile:       @echo  '  export_report   - List the usages of all
exported symbols'
Makefile:PHONY += includecheck versioncheck coccicheck export_report
Makefile:export_report:
Makefile:       $(PERL) $(srctree)/scripts/export_report.pl







-- 
Best Regards
Masahiro Yamada

      parent reply	other threads:[~2024-10-30  8:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-29 21:12 [PATCH] scripts: Remove export_report.pl Matthew Maurer
2024-10-29 23:52 ` Sami Tolvanen
2024-10-30  8:02 ` Masahiro Yamada [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=CAK7LNATYQAfsvU+Gm8FqBkKV-EMgHWD8Fp_mVrR5Uq81Lv5nEw@mail.gmail.com \
    --to=masahiroy@kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=mmaurer@google.com \
    --cc=samitolvanen@google.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;
as well as URLs for NNTP newsgroup(s).