linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+f2fs@kernel.org
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-hyperv@vger.kernel.org, linux-usb@vger.kernel.org,
	kvm@vger.kernel.org, dri-devel@lists.freedesktop.org,
	brcm80211@lists.linux.dev, ath10k@lists.infradead.org,
	linux-xfs@vger.kernel.org, dev@openvswitch.org,
	linux-s390@vger.kernel.org, linux-rdma@vger.kernel.org,
	linux-pm@vger.kernel.org, amd-gfx@lists.freedesktop.org,
	intel-xe@lists.freedesktop.org, linux-bcachefs@vger.kernel.org,
	iommu@lists.linux.dev, ath11k@lists.infradead.org,
	linux-media@vger.kernel.org, freedreno@lists.freedesktop.org,
	linux-cifs@vger.kernel.org, selinux@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, intel-gfx@lists.freedesktop.org,
	linux-erofs@lists.ozlabs.org, virtualization@lists.linux.dev,
	linux-sound@vger.kernel.org, linux-block@vger.kernel.org,
	ocfs2-devel@lists.linux.dev, mathieu.desnoyers@efficios.com,
	linux-cxl@vger.kernel.org, linux-tegra@vger.kernel.org,
	io-uring@vger.kernel.org, linux-edac@vger.kernel.org,
	linux-hwmon@vger.kernel.org, brcm80211-dev-list.pdl@broadcom.com,
	torvalds@linux-foundation.org, linuxppc-dev@lists.ozlabs.org,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net, Julia.Lawall@inria.fr,
	ath12k@lists.infradead.org,
	tipc-discussion@lists.sourceforge.net, mhiramat@kernel.org,
	netdev@vger.kernel.org, bpf@vger.kernel.org,
	linux-trace-kernel@vger.kernel.org, linux-wpan@vger.kernel.org,
	linux-nfs@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH] tracing/treewide: Remove second parameter of __assign_str()
Date: Wed, 12 Jun 2024 15:55:57 +0000	[thread overview]
Message-ID: <171820775738.32393.13116890369510221266.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240516133454.681ba6a0@rorschach.local.home>

Hello:

This patch was applied to jaegeuk/f2fs.git (dev)
by Steven Rostedt (Google) <rostedt@goodmis.org>:

On Thu, 16 May 2024 13:34:54 -0400 you wrote:
> From: "Steven Rostedt (Google)" <rostedt@goodmis.org>
> 
> [
>    This is a treewide change. I will likely re-create this patch again in
>    the second week of the merge window of v6.10 and submit it then. Hoping
>    to keep the conflicts that it will cause to a minimum.
> ]
> 
> [...]

Here is the summary with links:
  - [f2fs-dev] tracing/treewide: Remove second parameter of __assign_str()
    https://git.kernel.org/jaegeuk/f2fs/c/2c92ca849fcc

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html




_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

      parent reply	other threads:[~2024-06-12 15:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-16 17:34 [f2fs-dev] [PATCH] tracing/treewide: Remove second parameter of __assign_str() Steven Rostedt
2024-05-17  8:01 ` Christian König
2024-05-17  9:33 ` Thomas Hellström
2024-05-17  9:38 ` Rafael J. Wysocki
2024-05-17  9:50 ` Takashi Iwai
2024-05-17 16:23 ` Darrick J. Wong
2024-05-17 17:36 ` Guenter Roeck
2024-05-17 17:48   ` Steven Rostedt
2024-05-17 18:00     ` Guenter Roeck
2024-05-18  1:25       ` Guenter Roeck
2024-06-12 15:55 ` patchwork-bot+f2fs [this message]

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=171820775738.32393.13116890369510221266.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+f2fs@kernel.org \
    --cc=Julia.Lawall@inria.fr \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=ath10k@lists.infradead.org \
    --cc=ath11k@lists.infradead.org \
    --cc=ath12k@lists.infradead.org \
    --cc=bpf@vger.kernel.org \
    --cc=brcm80211-dev-list.pdl@broadcom.com \
    --cc=brcm80211@lists.linux.dev \
    --cc=dev@openvswitch.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=io-uring@vger.kernel.org \
    --cc=iommu@lists.linux.dev \
    --cc=kvm@vger.kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-bcachefs@vger.kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linux-wpan@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=ocfs2-devel@lists.linux.dev \
    --cc=rostedt@goodmis.org \
    --cc=selinux@vger.kernel.org \
    --cc=tipc-discussion@lists.sourceforge.net \
    --cc=torvalds@linux-foundation.org \
    --cc=virtualization@lists.linux.dev \
    /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).