From: Steven Rostedt <rostedt@goodmis.org>
To: Arun Easi <aeasi@marvell.com>
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Nilesh Javali <njavali@marvell.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
<GR-QLogic-Storage-Upstream@marvell.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
<linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-next <linux-next@vger.kernel.org>
Subject: Re: [EXT] build failure of next-20220906 due to 8bfc149ba24c ("scsi: qla2xxx: Enhance driver tracing with separate tunable and more")
Date: Tue, 6 Sep 2022 17:41:40 -0400 [thread overview]
Message-ID: <20220906174140.41b46a5f@gandalf.local.home> (raw)
In-Reply-To: <e9f5eb5e-3830-d19b-dcb0-05f7a36fcb2d@marvell.com>
On Tue, 6 Sep 2022 14:26:31 -0700
Arun Easi <aeasi@marvell.com> wrote:
> Steve, I was thinking both the fixes stay at least for a short
> term the one in qla2xxx to avoid tree dependencies.
>
> Since, the qla_def.h change goes as:
>
> +#ifndef CONFIG_TRACING
> +#ifndef trace_array_get_by_name
>
> ..it should co-exist when the "#define trace_array_get_by_name" gets
> merged in include/linux/trace.h. BTW, I will send out the changes to
> trace.h today.
>
> Other alternatives/suggestions welcome.
I doubt I'll have anything that conflicts with an update to
include/linux/trace.h, as it is seldom modified.
Just sent a patch out that updates that file and I'll review it, and then
you can push it through your tree.
-- Steve
next prev parent reply other threads:[~2022-09-06 21:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 14:32 build failure of next-20220906 due to 8bfc149ba24c ("scsi: qla2xxx: Enhance driver tracing with separate tunable and more") Sudip Mukherjee (Codethink)
2022-09-06 16:05 ` [EXT] " Arun Easi
2022-09-06 16:21 ` Steven Rostedt
2022-09-06 20:57 ` Sudip Mukherjee
2022-09-06 21:03 ` Steven Rostedt
2022-09-06 21:26 ` Arun Easi
2022-09-06 21:41 ` Steven Rostedt [this message]
2022-09-06 21:50 ` Arun Easi
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=20220906174140.41b46a5f@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=GR-QLogic-Storage-Upstream@marvell.com \
--cc=aeasi@marvell.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=njavali@marvell.com \
--cc=sudipm.mukherjee@gmail.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).