From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs: send: a couple trivial cleanups
Date: Thu, 6 Mar 2025 17:55:52 +0000 [thread overview]
Message-ID: <cover.1741283556.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
Simple cleanups, reduce code, details in the change logs.
Filipe Manana (2):
btrfs: send: remove unnecessary inode lookup at send_encoded_inline_extent()
btrfs: send: simplify return logic from send_encoded_extent()
fs/btrfs/send.c | 19 +++++--------------
1 file changed, 5 insertions(+), 14 deletions(-)
--
2.45.2
next reply other threads:[~2025-03-06 17:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 17:55 fdmanana [this message]
2025-03-06 17:55 ` [PATCH 1/2] btrfs: send: remove unnecessary inode lookup at send_encoded_inline_extent() fdmanana
2025-03-06 17:55 ` [PATCH 2/2] btrfs: send: simplify return logic from send_encoded_extent() fdmanana
2025-03-06 18:33 ` [PATCH 0/2] btrfs: send: a couple trivial cleanups David Sterba
2025-03-06 21:53 ` Qu Wenruo
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=cover.1741283556.git.fdmanana@suse.com \
--to=fdmanana@kernel.org \
--cc=linux-btrfs@vger.kernel.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