linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: hch@lst.de, torvalds@linux-foundation.org
Cc: david@fromorbit.com, linux-fsdevel@vger.kernel.org,
	linux-xfs@vger.kernel.org, ritesh.list@gmail.com,
	disgoel@linux.ibm.com, jack@suse.cz
Subject: [GIT PULL] iomap: new code for 6.4
Date: Thu, 27 Apr 2023 10:55:43 -0700	[thread overview]
Message-ID: <20230427175543.GA59213@frogsfrogsfrogs> (raw)

Hi Linus,

Please pull this branch with changes for iomap for 6.4-rc1.  The only
changes for this cycle are the addition of tracepoints to the iomap
directio code so that Ritesh (who is working on porting ext2 to iomap)
can observe the io flows more easily.  Dave will be sending you a pull
request for xfs code for this cycle.

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 09a9639e56c01c7a00d6c0ca63f4c7c41abe075d:

  Linux 6.3-rc6 (2023-04-09 11:15:57 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 3fd41721cd5c30af37c860e6201c98db0a568fd2:

  iomap: Add DIO tracepoints (2023-04-21 08:54:47 -0700)

----------------------------------------------------------------
New code for 6.4:

 * Remove an unused symbol.
 * Add tracepoints for the directio code.

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

----------------------------------------------------------------
Ritesh Harjani (IBM) (3):
      fs.h: Add TRACE_IOCB_STRINGS for use in trace points
      iomap: Remove IOMAP_DIO_NOSYNC unused dio flag
      iomap: Add DIO tracepoints

 fs/iomap/direct-io.c  |  9 ++++--
 fs/iomap/trace.c      |  1 +
 fs/iomap/trace.h      | 78 +++++++++++++++++++++++++++++++++++++++++++++++++++
 include/linux/fs.h    | 14 +++++++++
 include/linux/iomap.h |  6 ----
 5 files changed, 100 insertions(+), 8 deletions(-)

             reply	other threads:[~2023-04-27 17:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-27 17:55 Darrick J. Wong [this message]
2023-04-29 18:19 ` [GIT PULL] iomap: new code for 6.4 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=20230427175543.GA59213@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=david@fromorbit.com \
    --cc=disgoel@linux.ibm.com \
    --cc=hch@lst.de \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=ritesh.list@gmail.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).