From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux F2FS Dev Mailing List
<linux-f2fs-devel@lists.sourceforge.net>
Subject: [f2fs-dev] [GIT PULL] f2fs fix for 6.3-rc5
Date: Tue, 28 Mar 2023 17:33:59 -0700 [thread overview]
Message-ID: <ZCOHd4jYn8zUCEZ0@google.com> (raw)
Hi Linus,
Could you please consider this pull request?
Thanks,
The following changes since commit fe15c26ee26efa11741a7b632e9f23b01aca4cc6:
Linux 6.3-rc1 (2023-03-05 14:52:03 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git tags/f2fs-fix-6.3-rc5
for you to fetch changes up to 0b04d4c0542e8573a837b1d81b94209e48723b25:
f2fs: Fix f2fs_truncate_partial_nodes ftrace event (2023-03-10 08:57:49 -0800)
----------------------------------------------------------------
f2fs fix for 6.3-rc5
This fixes a tracepoint field size in f2fs, and another patch [1] to reveal this
bug comes in rc5 as well.
[1] https://patchwork.kernel.org/project/linux-trace-kernel/patch/20230309221302.642e82d9@gandalf.local.home/
----------------------------------------------------------------
Douglas Raillard (1):
f2fs: Fix f2fs_truncate_partial_nodes ftrace event
include/trace/events/f2fs.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux F2FS Dev Mailing List
<linux-f2fs-devel@lists.sourceforge.net>
Subject: [GIT PULL] f2fs fix for 6.3-rc5
Date: Tue, 28 Mar 2023 17:33:59 -0700 [thread overview]
Message-ID: <ZCOHd4jYn8zUCEZ0@google.com> (raw)
Hi Linus,
Could you please consider this pull request?
Thanks,
The following changes since commit fe15c26ee26efa11741a7b632e9f23b01aca4cc6:
Linux 6.3-rc1 (2023-03-05 14:52:03 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git tags/f2fs-fix-6.3-rc5
for you to fetch changes up to 0b04d4c0542e8573a837b1d81b94209e48723b25:
f2fs: Fix f2fs_truncate_partial_nodes ftrace event (2023-03-10 08:57:49 -0800)
----------------------------------------------------------------
f2fs fix for 6.3-rc5
This fixes a tracepoint field size in f2fs, and another patch [1] to reveal this
bug comes in rc5 as well.
[1] https://patchwork.kernel.org/project/linux-trace-kernel/patch/20230309221302.642e82d9@gandalf.local.home/
----------------------------------------------------------------
Douglas Raillard (1):
f2fs: Fix f2fs_truncate_partial_nodes ftrace event
include/trace/events/f2fs.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
next reply other threads:[~2023-03-29 0:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 0:33 Jaegeuk Kim [this message]
2023-03-29 0:33 ` [GIT PULL] f2fs fix for 6.3-rc5 Jaegeuk Kim
2023-03-29 17:41 ` [f2fs-dev] " pr-tracker-bot
2023-03-29 17:41 ` pr-tracker-bot
2023-03-29 22:21 ` patchwork-bot+f2fs
2023-03-29 22:21 ` 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=ZCOHd4jYn8zUCEZ0@google.com \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.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 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.