From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Denis Efremov <efremov@linux.com>
Cc: Michal Marek <michal.lkml@markovi.net>,
Emil Velikov <emil.l.velikov@gmail.com>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] modpost: check for static EXPORT_SYMBOL* functions
Date: Sun, 28 Jul 2019 11:00:06 +0900 [thread overview]
Message-ID: <CAK7LNAR5AM_fU36_9vc9wVJhxbzD5Xc72-mqBw6M3k_-9KZjjQ@mail.gmail.com> (raw)
In-Reply-To: <5232680b-5303-3d63-db51-de65eea76e3a@linux.com>
Hi.
On Sun, Jul 28, 2019 at 4:14 AM Denis Efremov <efremov@linux.com> wrote:
>
> Hi.
>
> > Could you drop the solved ones from the list?
>
> Yes, of course. Do you want me to remove all symbols fixed with patches
> or only those are in-tree now?
>
> Should it be like this:
> 1. "torture_onoff_cleanup" [kernel/torture]
> "torture_shuffle_cleanup" [kernel/torture]
> Patch: https://lkml.org/lkml/2019/7/4/411 (accepted)
> 2. "LZ4HC_setExternalDict" [lib/lz4/lz4hc_compress]
> Patch: https://lkml.org/lkml/2019/7/8/842
> 3. "drm_client_close" [drivers/gpu/drm/drm]
> Patch: https://lkml.org/lkml/2019/7/3/758 (accepted)
> 4. "ahci_em_messages" [drivers/ata/libahci]
> Patch: https://lkml.org/lkml/2019/7/10/550 (reviewed)
> 5. "ftrace_set_clr_event" [vmlinux]
> Patch: https://lkml.org/lkml/2019/7/4/609 (reviewed)
> 6. "rmi_2d_sensor_set_input_params" [drivers/input/rmi4/rmi_core]
> Patch: https://lkml.org/lkml/2019/7/8/999 (accepted)
> 10. "empty_zero_page" [vmlinux]
> 11. "phys_base" [vmlinux]
> 12. "hypercall_page" [vmlinux]
>
> Or like this:
> 1. "empty_zero_page" [vmlinux]
> 2. "phys_base" [vmlinux]
> 3. "hypercall_page" [vmlinux]
>
> Well, I could remove this list at all. It seems like the following list
> with existing commits is enough to show the problem of static exported
> functions.
Yeah, I agree.
Showing some existing commits is enough.
> I will resend the patch shortly after.
>
> Regards,
> Denis
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2019-07-28 2:00 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-14 15:28 [RFC PATCH] modpost: check for static EXPORT_SYMBOL* functions Denis Efremov
2019-07-15 14:43 ` Emil Velikov
2019-07-27 12:55 ` Masahiro Yamada
2019-07-27 19:13 ` Denis Efremov
2019-07-28 2:00 ` Masahiro Yamada [this message]
2019-07-28 10:09 ` [PATCH] " Denis Efremov
2019-07-29 3:29 ` Masahiro Yamada
2019-07-29 9:51 ` Denis Efremov
2019-07-29 5:13 ` Stephen Rothwell
2019-07-29 9:16 ` Denis Efremov
2019-07-29 9:32 ` Masahiro Yamada
2019-07-29 12:40 ` Stephen Rothwell
2019-07-29 12:52 ` Denis Efremov
2019-07-29 13:07 ` Stephen Rothwell
2019-07-29 9:22 ` [PATCH v2] " Denis Efremov
2019-07-29 12:20 ` Stephen Rothwell
2019-07-29 12:47 ` Denis Efremov
2019-07-29 14:18 ` [PATCH v3] " Denis Efremov
2019-07-29 22:26 ` Stephen Rothwell
2019-07-30 6:59 ` Denis Efremov
2019-07-30 16:29 ` Masahiro Yamada
2019-07-30 16:44 ` Denis Efremov
2019-07-30 17:21 ` Masahiro Yamada
2019-07-30 18:11 ` [PATCH v4] " Denis Efremov
2019-07-30 18:15 ` Denis Efremov
2019-07-31 8:54 ` Masahiro Yamada
2019-08-01 2:20 ` Masahiro Yamada
2019-08-01 6:17 ` Denis Efremov
2019-08-01 6:06 ` [PATCH v5] " Denis Efremov
2019-08-07 15:12 ` Masahiro Yamada
2019-08-13 16:07 ` Masahiro Yamada
2019-08-13 21:11 ` Denis Efremov
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=CAK7LNAR5AM_fU36_9vc9wVJhxbzD5Xc72-mqBw6M3k_-9KZjjQ@mail.gmail.com \
--to=yamada.masahiro@socionext.com \
--cc=efremov@linux.com \
--cc=emil.l.velikov@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
/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).