From: "Darrick J. Wong" <djwong@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
david@fromorbit.com, linux-kernel@vger.kernel.org,
sandeen@sandeen.net, hch@lst.de
Subject: [GIT PULL] iomap: one more change for 5.13-rc1
Date: Thu, 6 May 2021 17:37:48 -0700 [thread overview]
Message-ID: <20210507003748.GG8582@magnolia> (raw)
Hi Linus,
Please pull this second patch to the iomap code for 5.13-rc1, which
removes a now-unused field from one of the iomap structs. I don't know
if Christoph intends to send a %pD fix for last week's swapfile patch;
so far he hasn't sent me anything...
The branch merges cleanly with upstream as of a few minutes ago. Please
let me know if there are any strange problems.
--D
The following changes since commit 5e321ded302da4d8c5d5dd953423d9b748ab3775:
Merge tag 'for-5.13/parisc' of git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux (2021-05-03 13:47:17 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/iomap-5.13-merge-3
for you to fetch changes up to 6e552494fb90acae005d74ce6a2ee102d965184b:
iomap: remove unused private field from ioend (2021-05-04 08:54:29 -0700)
----------------------------------------------------------------
More new code for 5.13-rc1:
- Remove the now unused "io_private" field from struct iomap_ioend, for
a modest savings in memory allocation.
----------------------------------------------------------------
Brian Foster (1):
iomap: remove unused private field from ioend
fs/iomap/buffered-io.c | 7 +------
fs/xfs/xfs_aops.c | 2 +-
include/linux/iomap.h | 5 +----
3 files changed, 3 insertions(+), 11 deletions(-)
next reply other threads:[~2021-05-07 0:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 0:37 Darrick J. Wong [this message]
2021-05-07 7:51 ` [GIT PULL] iomap: one more change for 5.13-rc1 pr-tracker-bot
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=20210507003748.GG8582@magnolia \
--to=djwong@kernel.org \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
--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