linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: david@fromorbit.com, djwong@kernel.org, hch@lst.de,
	torvalds@linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
	luhongfei@vivo.com
Subject: [GIT PULL] iomap: new code for 6.5
Date: Sun, 2 Jul 2023 09:22:55 -0700	[thread overview]
Message-ID: <168831482682.535407.9162875426107097138.stg-ugh@frogsfrogsfrogs> (raw)

Hi Linus,

Please pull this branch with changes for iomap for 6.5-rc1.

As usual, I did a test-merge with the main upstream branch as of a few
minutes ago, and didn't see any conflicts.  Please let me know if you
encounter any problems.

--D

The following changes since commit 858fd168a95c5b9669aac8db6c14a9aeab446375:

Linux 6.4-rc6 (2023-06-11 14:35:30 -0700)

are available in the Git repository at:

git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/iomap-6.5-merge-1

for you to fetch changes up to 447a0bc108e4bae4c1ea845aacf43c10c28814e8:

iomap: drop me [hch] from MAINTAINERS for iomap (2023-06-29 09:22:51 -0700)

----------------------------------------------------------------
New code for 6.5:

* Fix a type signature mismatch.
* Drop Christoph as maintainer.

Signed-off-by: Darrick J. Wong <djwong@kernel.org>

----------------------------------------------------------------
Christoph Hellwig (1):
iomap: drop me [hch] from MAINTAINERS for iomap

Lu Hongfei (1):
fs: iomap: Change the type of blocksize from 'int' to 'unsigned int' in iomap_file_buffered_write_punch_delalloc

MAINTAINERS            | 1 -
fs/iomap/buffered-io.c | 2 +-
2 files changed, 1 insertion(+), 2 deletions(-)

             reply	other threads:[~2023-07-02 16:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-02 16:22 Darrick J. Wong [this message]
2023-07-02 18:53 ` [GIT PULL] iomap: new code for 6.5 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=168831482682.535407.9162875426107097138.stg-ugh@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=david@fromorbit.com \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=luhongfei@vivo.com \
    --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).