From: Al Viro <viro@zeniv.linux.org.uk>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Christoph Hellwig <hch@infradead.org>
Subject: Re: [RFC][PATCHES] convert ->getgeo() from block_device of partition to gendisk
Date: Wed, 3 Sep 2025 21:07:37 +0100 [thread overview]
Message-ID: <20250903200737.GM39973@ZenIV> (raw)
In-Reply-To: <b0de8c00-050f-45ee-9a77-72d12159fed5@kernel.dk>
On Wed, Sep 03, 2025 at 12:58:32PM -0600, Jens Axboe wrote:
> > Which tree would you prefer it to go through? Currently it's in viro/vfs.git
> > #work.getgeo (rebased to 6.17-rc1, no changes since the last posting);
> > I can merge it into vfs/viro #for-next and push it to Linus in the next
> > window, unless you prefer it to go through the block tree...
>
> Assuming it merges cleanly with my for-6.18/block tree, which I believe
> it should as there's not that much in there, I'm fine with it going in
> via your vfs tree. Which is also why I provided my acked-by. It probably
> _should_ go in via the block tree, but little risk of complications
> here, so...
I can send a pull request to you just as easily as to Linus, so if you would
prefer it in your tree - not a problem:
The following changes since commit 8f5ae30d69d7543eee0d70083daf4de8fe15d585:
Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-getgeo
for you to fetch changes up to 4fc8728aa34f54835b72e4db0f3db76a72948b65:
block: switch ->getgeo() to struct gendisk (2025-08-13 02:59:29 -0400)
----------------------------------------------------------------
switching ->getgeo() from struct block_device to struct gendisk
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
----------------------------------------------------------------
Al Viro (3):
scsi: switch scsi_bios_ptable() and scsi_partsize() to gendisk
scsi: switch ->bios_param() to passing gendisk
block: switch ->getgeo() to struct gendisk
Documentation/filesystems/locking.rst | 2 +-
Documentation/scsi/scsi_mid_low_api.rst | 8 ++++----
arch/m68k/emu/nfblock.c | 4 ++--
arch/um/drivers/ubd_kern.c | 6 +++---
block/ioctl.c | 4 ++--
block/partitions/ibm.c | 2 +-
drivers/ata/libata-scsi.c | 4 ++--
drivers/block/amiflop.c | 10 +++++-----
drivers/block/aoe/aoeblk.c | 4 ++--
drivers/block/floppy.c | 4 ++--
drivers/block/mtip32xx/mtip32xx.c | 6 +++---
drivers/block/rnbd/rnbd-clt.c | 4 ++--
drivers/block/sunvdc.c | 3 +--
drivers/block/swim.c | 4 ++--
drivers/block/virtio_blk.c | 6 +++---
drivers/block/xen-blkfront.c | 4 ++--
drivers/md/dm.c | 4 ++--
drivers/md/md.c | 4 ++--
drivers/memstick/core/ms_block.c | 4 ++--
drivers/memstick/core/mspro_block.c | 4 ++--
drivers/message/fusion/mptscsih.c | 2 +-
drivers/message/fusion/mptscsih.h | 2 +-
drivers/mmc/core/block.c | 4 ++--
drivers/mtd/mtd_blkdevs.c | 4 ++--
drivers/mtd/ubi/block.c | 4 ++--
drivers/nvdimm/btt.c | 4 ++--
drivers/nvme/host/core.c | 4 ++--
drivers/nvme/host/nvme.h | 2 +-
drivers/s390/block/dasd.c | 7 ++++---
drivers/scsi/3w-9xxx.c | 2 +-
drivers/scsi/3w-sas.c | 2 +-
drivers/scsi/3w-xxxx.c | 2 +-
drivers/scsi/BusLogic.c | 4 ++--
drivers/scsi/BusLogic.h | 2 +-
drivers/scsi/aacraid/linit.c | 6 +++---
drivers/scsi/advansys.c | 2 +-
drivers/scsi/aha152x.c | 4 ++--
drivers/scsi/aha1542.c | 2 +-
drivers/scsi/aha1740.c | 2 +-
drivers/scsi/aic7xxx/aic79xx_osm.c | 4 ++--
drivers/scsi/aic7xxx/aic7xxx_osm.c | 4 ++--
drivers/scsi/arcmsr/arcmsr_hba.c | 6 +++---
drivers/scsi/atp870u.c | 2 +-
drivers/scsi/fdomain.c | 4 ++--
drivers/scsi/imm.c | 2 +-
drivers/scsi/initio.c | 4 ++--
drivers/scsi/ipr.c | 8 ++++----
drivers/scsi/ips.c | 2 +-
drivers/scsi/ips.h | 2 +-
drivers/scsi/libsas/sas_scsi_host.c | 2 +-
drivers/scsi/megaraid.c | 4 ++--
drivers/scsi/megaraid.h | 2 +-
drivers/scsi/megaraid/megaraid_sas_base.c | 4 ++--
drivers/scsi/mpi3mr/mpi3mr_os.c | 4 ++--
drivers/scsi/mpt3sas/mpt3sas_scsih.c | 4 ++--
drivers/scsi/mvumi.c | 2 +-
drivers/scsi/myrb.c | 2 +-
drivers/scsi/pcmcia/sym53c500_cs.c | 2 +-
drivers/scsi/ppa.c | 2 +-
drivers/scsi/qla1280.c | 2 +-
drivers/scsi/qlogicfas408.c | 2 +-
drivers/scsi/qlogicfas408.h | 2 +-
drivers/scsi/scsicam.c | 16 ++++++++--------
drivers/scsi/sd.c | 8 ++++----
drivers/scsi/stex.c | 2 +-
drivers/scsi/storvsc_drv.c | 2 +-
drivers/scsi/wd719x.c | 2 +-
include/linux/blkdev.h | 2 +-
include/linux/libata.h | 2 +-
include/scsi/libsas.h | 2 +-
include/scsi/scsi_host.h | 2 +-
include/scsi/scsicam.h | 7 ++++---
72 files changed, 135 insertions(+), 134 deletions(-)
next prev parent reply other threads:[~2025-09-03 20:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 19:26 [RFC][PATCHES] convert ->getgeo() from block_device of partition to gendisk Al Viro
2025-07-18 19:27 ` [RFC][PATCH 1/3] scsi: switch scsi_bios_ptable() and scsi_partsize() " Al Viro
2025-07-18 19:28 ` [RFC][PATCH 2/3] scsi: switch ->bios_param() to passing gendisk Al Viro
2025-07-18 19:29 ` [RFC][PATCH 3/3] block: switch ->getgeo() to struct gendisk Al Viro
2025-07-18 21:20 ` [RFC][PATCHES] convert ->getgeo() from block_device of partition to gendisk Jens Axboe
2025-09-03 14:09 ` Al Viro
2025-09-03 18:58 ` Jens Axboe
2025-09-03 20:07 ` Al Viro [this message]
2025-09-03 21:16 ` Jens Axboe
2025-07-21 6:27 ` Christoph Hellwig
2025-07-22 3:30 ` Martin K. Petersen
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=20250903200737.GM39973@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=linux-block@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