From: Randy Dunlap <rdunlap@infradead.org>
To: Jacob Keller <jacob.e.keller@intel.com>, linux-kbuild@vger.kernel.org
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: [RFC PATCH] scripts: remove namespace.pl
Date: Thu, 8 Oct 2020 17:09:19 -0700 [thread overview]
Message-ID: <0bff6c13-bcf1-4854-dc12-826979f24ed5@infradead.org> (raw)
In-Reply-To: <20201008232559.2866491-1-jacob.e.keller@intel.com>
On 10/8/20 4:25 PM, Jacob Keller wrote:
[snip]
> However, given the discussion at [2], I suspect that few people are
> actively using this tool. It doesn't have a maintainer in the
> MAINTAINERS flie, and it produces so many warnings for unused symbols
> that it is difficult to use effectively. Thus, I propose we simply
> remove it.
Agreed. I don't see any evidence that anyone is using it.
Goodbye.
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> [1] https://lore.kernel.org/netdev/20200708164812.384ae8ea@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com/
> [2] https://lore.kernel.org/lkml/20190129204319.15238-1-jacob.e.keller@intel.com/
> [3] https://lore.kernel.org/netdev/20190828.154744.2058157956381129672.davem@davemloft.net/
> [4] https://lore.kernel.org/netdev/20190827210928.576c5fef@cakuba.netronome.com/
>
> Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
> Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
> Cc: Randy Dunlap <rdunlap@infradead.org>
> Cc: Jakub Kicinski <kuba@kernel.org>
> ---
> Documentation/process/submit-checklist.rst | 3 +-
> Makefile | 6 +-
> scripts/namespace.pl | 473 ---------------------
> 3 files changed, 2 insertions(+), 480 deletions(-)
> delete mode 100755 scripts/namespace.pl
--
~Randy
next prev parent reply other threads:[~2020-10-09 0:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 23:25 [RFC PATCH] scripts: remove namespace.pl Jacob Keller
2020-10-09 0:09 ` Randy Dunlap [this message]
2020-10-10 2:39 ` Masahiro Yamada
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=0bff6c13-bcf1-4854-dc12-826979f24ed5@infradead.org \
--to=rdunlap@infradead.org \
--cc=jacob.e.keller@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=yamada.masahiro@socionext.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).