From: Steven Rostedt <rostedt@goodmis.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: patchwork-bot+f2fs@kernel.org,
Douglas RAILLARD <douglas.raillard@arm.com>,
chao@kernel.org, mhiramat@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [f2fs-dev] [PATCH] f2fs: Fix f2fs_truncate_partial_nodes ftrace event
Date: Tue, 28 Mar 2023 21:01:31 -0400 [thread overview]
Message-ID: <20230328210131.7a057a63@gandalf.local.home> (raw)
In-Reply-To: <ZCOH9pc3hBKU3G3Z@google.com>
On Tue, 28 Mar 2023 17:36:06 -0700
Jaegeuk Kim <jaegeuk@kernel.org> wrote:
> > I'm hoping you are not waiting for the merge window to get this in. Please
> > get it to Linus before rc5 is out, because I plan on adding my patch[1]
> > which will cause this to fail the build at rc5.
> >
> > The above is a fix to bug that causes unwanted results. Please get it into
> > mainline ASAP.
>
> Thanks for heads-up. I sent a pull request having the above patch to Linus.
>
> https://lore.kernel.org/linux-f2fs-devel/ZCOHd4jYn8zUCEZ0@google.com/T/#u
Much appreciated!
-- Steve
next prev parent reply other threads:[~2023-03-29 1:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 12:25 [PATCH] f2fs: Fix f2fs_truncate_partial_nodes ftrace event Douglas RAILLARD
2023-03-06 12:51 ` Mukesh Ojha
2023-03-06 16:15 ` Steven Rostedt
2023-03-06 17:25 ` Steven Rostedt
2023-03-07 6:01 ` Chao Yu
2023-03-07 17:40 ` [f2fs-dev] " patchwork-bot+f2fs
2023-03-28 23:03 ` Steven Rostedt
2023-03-29 0:36 ` Jaegeuk Kim
2023-03-29 1:01 ` Steven Rostedt [this message]
2023-03-29 17:41 ` Linus Torvalds
2023-08-14 13:32 ` Kajetan Puchalski
2023-08-14 14:39 ` Kajetan Puchalski
2023-08-14 20:37 ` Jaegeuk Kim
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=20230328210131.7a057a63@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=chao@kernel.org \
--cc=douglas.raillard@arm.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=patchwork-bot+f2fs@kernel.org \
--cc=torvalds@linux-foundation.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 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).