From: John Hubbard <jhubbard@nvidia•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for Aug 23
Date: Fri, 23 Aug 2019 19:37:55 -0700 [thread overview]
Message-ID: <47bf2ffc-a737-e4ba-8d37-96472f307094@nvidia.com> (raw)
In-Reply-To: <20190823192658.49e6f68d@canb.auug.org.au>
On 8/23/19 2:26 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190822:
>
> The thermal tree gained a conflict against the jc_docs tree.
>
> The rdma tree gained a conflict against the rdma-fixes tree.
>
> The net-next tree gained conflicts against the pci tree.
>
> The crypto tree gained a conflict against Linus' tree.
>
> The drm tree gained a conflict against the drm-fixes tree.
Hi,
Even though I saw email proposing fixes for one (maybe both) of the
following warnings, I'm still seeing them in this linux-next:
WARNING: "ahci_em_messages" [drivers/ata/libahci] is a static EXPORT_SYMBOL_GPL
WARNING: "ftrace_set_clr_event" [vmlinux] is a static EXPORT_SYMBOL_GPL
...and obviously these can be trivially fixed by:
diff --git a/drivers/ata/libahci.c b/drivers/ata/libahci.c
index e4c45d3cca79..bff369d9a1a7 100644
--- a/drivers/ata/libahci.c
+++ b/drivers/ata/libahci.c
@@ -175,7 +175,6 @@ struct ata_port_operations ahci_pmp_retry_srst_ops = {
EXPORT_SYMBOL_GPL(ahci_pmp_retry_srst_ops);
static bool ahci_em_messages __read_mostly = true;
-EXPORT_SYMBOL_GPL(ahci_em_messages);
module_param(ahci_em_messages, bool, 0444);
/* add other LED protocol types when they become supported */
MODULE_PARM_DESC(ahci_em_messages,
diff --git a/kernel/trace/trace_events.c b/kernel/trace/trace_events.c
index c7506bc81b75..648930823b57 100644
--- a/kernel/trace/trace_events.c
+++ b/kernel/trace/trace_events.c
@@ -787,7 +787,7 @@ static int __ftrace_set_clr_event(struct trace_array *tr, const char *match,
return ret;
}
-static int ftrace_set_clr_event(struct trace_array *tr, char *buf, int set)
+int ftrace_set_clr_event(struct trace_array *tr, char *buf, int set)
{
char *event = NULL, *sub = NULL, *match;
int ret;
...which I didn't create patches for, because I expect they are already
in flight. But if those somehow got lost or skipped, then here's an early
warning that these fixes still need to be applied.
thanks,
--
John Hubbard
NVIDIA
next prev parent reply other threads:[~2019-08-24 2:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 9:26 linux-next: Tree for Aug 23 Stephen Rothwell
2019-08-24 2:37 ` John Hubbard [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-23 3:37 Stephen Rothwell
2023-08-23 6:14 Stephen Rothwell
2022-08-23 5:26 Stephen Rothwell
2021-08-23 10:26 Stephen Rothwell
2018-08-23 3:32 Stephen Rothwell
2017-08-23 7:09 Stephen Rothwell
2016-08-23 4:55 Stephen Rothwell
2014-08-22 22:04 Stephen Rothwell
2014-08-25 4:57 ` Guenter Roeck
2014-09-01 15:58 ` Peter Zijlstra
2014-09-01 16:46 ` Guenter Roeck
2014-09-01 19:04 ` Peter Zijlstra
2014-09-02 9:40 ` Peter Zijlstra
2014-09-02 9:55 ` Peter Zijlstra
2014-09-02 19:04 ` Guenter Roeck
2014-09-02 20:21 ` Peter Zijlstra
2014-09-02 23:50 ` Guenter Roeck
2014-09-02 17:59 ` Guenter Roeck
2012-08-23 5:22 Stephen Rothwell
2011-08-23 6:04 Stephen Rothwell
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=47bf2ffc-a737-e4ba-8d37-96472f307094@nvidia.com \
--to=jhubbard@nvidia$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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