All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [GIT PULL] FIEMAP cleanups for 5.15-rc1
Date: Wed, 25 Aug 2021 14:53:09 +0200	[thread overview]
Message-ID: <20210825125309.GA8508@quack2.suse.cz> (raw)
In-Reply-To: <20210825124920.GF14620@quack2.suse.cz>

Forgot to CC fsdevel so adding it now.

								Honza
On Wed 25-08-21 14:49:20, Jan Kara wrote:
>   Hello Linus,
> 
>   Another early pull request for the merge window due to clashing holidays.
> Could you please pull from
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git fiemap_for_v5.15-rc1
> 
> to get FIEMAP cleanups from Christoph transitioning all remaining
> filesystems supporting FIEMAP (ext2, hpfs) to iomap API and removing the
> old helper.
> 
> Top of the tree is 9acb9c48b940. The full shortlog is:
> 
> Christoph Hellwig (4):
>       ext2: make ext2_iomap_ops available unconditionally
>       ext2: use iomap_fiemap to implement ->fiemap
>       hpfs: use iomap_fiemap to implement ->fiemap
>       fs: remove generic_block_fiemap
> 
> The diffstat is
> 
>  fs/ext2/Kconfig        |   1 +
>  fs/ext2/inode.c        |  15 ++--
>  fs/hpfs/Kconfig        |   1 +
>  fs/hpfs/file.c         |  51 ++++++++++++-
>  fs/ioctl.c             | 203 -------------------------------------------------
>  include/linux/fiemap.h |   4 -
>  6 files changed, 60 insertions(+), 215 deletions(-)
> 
> 							Thanks
> 								Honza
> -- 
> Jan Kara <jack@suse.com>
> SUSE Labs, CR
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

       reply	other threads:[~2021-08-25 12:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210825124920.GF14620@quack2.suse.cz>
2021-08-25 12:53 ` Jan Kara [this message]
2021-08-30 17:42   ` [GIT PULL] FIEMAP cleanups for 5.15-rc1 Linus Torvalds

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=20210825125309.GA8508@quack2.suse.cz \
    --to=jack@suse.cz \
    --cc=linux-fsdevel@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.