Re: [PATCH 2/2] block: pass a phys_addr_t to get_max_segment_size

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
Subject: Re: [PATCH 2/2] block: pass a phys_addr_t to get_max_segment_size
From: Christoph Hellwig <hch@xxxxxx>
Date: Wed, 10 Jul 2024 07:52:03 +0200
Cc: Christoph Hellwig <hch@xxxxxx>, Jens Axboe <axboe@xxxxxxxxx>, linux-m68k@xxxxxxxxxxxxxxx, linux-block@xxxxxxxxxxxxxxx, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>
In-reply-to: <CAMuHMdV95g78=2GmLP95Kn3_0DL5zVuv2KCDYVsk8D2gNnu7SQ@mail.gmail.com>
References: <20240706075228.2350978-1-hch@lst.de> <20240706075228.2350978-3-hch@lst.de> <CAMuHMdV95g78=2GmLP95Kn3_0DL5zVuv2KCDYVsk8D2gNnu7SQ@mail.gmail.com>
User-agent: Mutt/1.5.17 (2007-11-01)

Hi Geert,

the fix is queued up here:

https://git.kernel.dk/cgit/linux-block/commit/?h=for-6.11/block&id=61353a63a22890f2c642232ae1ab4a2e02e6a27c

and should be in linux-next.  And next time I need to do a full
retest after doing your suggested patch order change :)

Follow-Ups:
- Re: [PATCH 2/2] block: pass a phys_addr_t to get_max_segment_size
  - From: Geert Uytterhoeven

References:
- add a bvec_phys helper v3
  - From: Christoph Hellwig
- [PATCH 2/2] block: pass a phys_addr_t to get_max_segment_size
  - From: Christoph Hellwig
- Re: [PATCH 2/2] block: pass a phys_addr_t to get_max_segment_size
  - From: Geert Uytterhoeven

Prev by Date: Re: fine-grained PI control
Next by Date: Re: [PATCH 1/2] block: also check bio alignment for bio based drivers
Previous by thread: Re: [PATCH 2/2] block: pass a phys_addr_t to get_max_segment_size
Next by thread: Re: [PATCH 2/2] block: pass a phys_addr_t to get_max_segment_size
Index(es):
- Date
- Thread

[Index of Archives] [Linux RAID] [Linux SCSI] [Linux ATA RAID] [IDE] [Linux Wireless] [Linux Kernel] [ATH6KL] [Linux Bluetooth] [Linux Netdev] [Kernel Newbies] [Security] [Git] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Device Mapper]