From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Linux Trace Kernel" <linux-trace-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
intel-gfx@lists.freedesktop.org,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"David Airlie" <airlied@gmail.com>
Subject: Re: [PATCH] drm/i915: Add missing ; to __assign_str() macros in tracepoint code
Date: Thu, 22 Feb 2024 14:04:20 -0500 [thread overview]
Message-ID: <ZdeatNbtahdEWMXV@intel.com> (raw)
In-Reply-To: <20240222134349.1e9a155d@gandalf.local.home>
On Thu, Feb 22, 2024 at 01:43:49PM -0500, Steven Rostedt wrote:
> On Thu, 22 Feb 2024 13:30:57 -0500
> Steven Rostedt <rostedt@goodmis.org> wrote:
>
> > From: "Steven Rostedt (Google)" <rostedt@goodmis.org>
> >
> > I'm working on improving the __assign_str() and __string() macros to be
> > more efficient, and removed some unneeded semicolons. This triggered a bug
> > in the build as some of the __assign_str() macros in intel_display_trace
> > was missing a terminating semicolon.
> >
> > Fixes: 2ceea5d88048b ("drm/i915: Print plane name in fbc tracepoints")
> > Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
> > ---
>
> Note, I have patches that depend on this fix, so if one of the maintainers
> would like to just give me an "Acked-by", I'll take it through my tree. I
> doubt it will have any conflicts, unless you are planning on changing the
> given effected events.
since it is not breaking builds on our side and the conflicts, if any, would
be minimal, feel free to take this trough your tree
Acked-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>
> -- Steve
next prev parent reply other threads:[~2024-02-22 19:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 18:30 [PATCH] drm/i915: Add missing ; to __assign_str() macros in tracepoint code Steven Rostedt
2024-02-22 18:33 ` ✓ CI.Patch_applied: success for " Patchwork
2024-02-22 18:34 ` ✗ CI.checkpatch: warning " Patchwork
2024-02-22 18:34 ` ✓ CI.KUnit: success " Patchwork
2024-02-22 18:42 ` [PATCH] " Ville Syrjälä
2024-02-22 18:46 ` Steven Rostedt
2024-02-22 18:43 ` Steven Rostedt
2024-02-22 19:04 ` Rodrigo Vivi [this message]
2024-02-22 19:27 ` Steven Rostedt
2024-02-22 18:45 ` ✓ CI.Build: success for " Patchwork
2024-02-22 18:46 ` ✓ CI.Hooks: " Patchwork
2024-02-22 18:47 ` ✗ CI.checksparse: warning " Patchwork
2024-02-22 19:07 ` ✓ CI.BAT: success " Patchwork
2024-02-23 2:35 ` ✗ Fi.CI.CHECKPATCH: warning " Patchwork
2024-02-23 2:49 ` ✓ Fi.CI.BAT: success " Patchwork
2024-02-23 16:56 ` ✓ Fi.CI.IGT: " Patchwork
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=ZdeatNbtahdEWMXV@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=ville.syrjala@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.