From: Jani Nikula <jani.nikula@linux.intel.com>
To: Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux trace kernel <linux-trace-kernel@vger.kernel.org>
Subject: Re: [PATCH] tracing/treewide: Remove second parameter of __assign_str()
Date: Fri, 17 May 2024 10:08:51 +0300 [thread overview]
Message-ID: <87eda0c3uk.fsf@intel.com> (raw)
In-Reply-To: <20240516133454.681ba6a0@rorschach.local.home>
On Thu, 16 May 2024, Steven Rostedt <rostedt@goodmis.org> wrote:
> There's over 700 users of __assign_str() and because coccinelle does not
> handle the TRACE_EVENT() macro I ended up using the following sed script:
>
> git grep -l __assign_str | while read a ; do
> sed -e 's/\(__assign_str([^,]*[^ ,]\) *,[^;]*/\1)/' $a > /tmp/test-file;
> mv /tmp/test-file $a;
> done
Try 'sed -i' ;)
> .../drm/i915/display/intel_display_trace.h | 56 ++++-----
On i915,
Acked-by: Jani Nikula <jani.nikula@intel.com>
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-05-17 7:08 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 17:34 [PATCH] tracing/treewide: Remove second parameter of __assign_str() Steven Rostedt
2024-05-16 17:34 ` Steven Rostedt
2024-05-16 17:34 ` [f2fs-dev] " Steven Rostedt
2024-05-16 17:40 ` ✗ CI.Patch_applied: failure for tracing/treewide: Remove second parameter of __assign_str() (rev3) Patchwork
2024-05-16 18:25 ` ✗ Fi.CI.BUILD: " Patchwork
2024-05-17 7:08 ` Jani Nikula [this message]
2024-05-17 14:16 ` [PATCH] tracing/treewide: Remove second parameter of __assign_str() Steven Rostedt
2024-05-17 8:01 ` Christian König
2024-05-17 8:01 ` Christian König
2024-05-17 8:01 ` [f2fs-dev] " Christian König
2024-05-17 9:33 ` Thomas Hellström
2024-05-17 9:33 ` Thomas Hellström
2024-05-17 9:33 ` [f2fs-dev] " Thomas Hellström
2024-05-17 9:38 ` Rafael J. Wysocki
2024-05-17 9:38 ` [f2fs-dev] " Rafael J. Wysocki
2024-05-17 9:38 ` Rafael J. Wysocki
2024-05-17 9:50 ` Takashi Iwai
2024-05-17 9:50 ` Takashi Iwai
2024-05-17 9:50 ` [f2fs-dev] " Takashi Iwai
2024-05-17 16:23 ` Darrick J. Wong
2024-05-17 16:23 ` [f2fs-dev] " Darrick J. Wong
2024-05-17 16:23 ` Darrick J. Wong
2024-05-17 17:36 ` Guenter Roeck
2024-05-17 17:36 ` [f2fs-dev] " Guenter Roeck
2024-05-17 17:36 ` Guenter Roeck
2024-05-17 17:48 ` Steven Rostedt
2024-05-17 17:48 ` [f2fs-dev] " Steven Rostedt
2024-05-17 17:48 ` Steven Rostedt
2024-05-17 18:00 ` Guenter Roeck
2024-05-17 18:00 ` [f2fs-dev] " Guenter Roeck
2024-05-17 18:00 ` Guenter Roeck
2024-05-18 1:25 ` Guenter Roeck
2024-05-18 1:25 ` [f2fs-dev] " Guenter Roeck
2024-05-18 1:25 ` Guenter Roeck
2024-06-12 15:55 ` [f2fs-dev] " patchwork-bot+f2fs
2024-06-12 15:55 ` patchwork-bot+f2fs
2024-06-12 15:55 ` patchwork-bot+f2fs
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=87eda0c3uk.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
/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.