The pull request you sent on Fri, 17 Jun 2022 12:22:54 -0400:
> git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git
> tags/for-5.19/dm-fixes-3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/274295c6e53f8b8b8dfa8b24a3fcb8a9d670c22c
Thank you!
--
Hi Linus,
The following changes since commit b13baccc3850ca8b8cccbf8ed9912dbaa0fdf7f3:
Linux 5.19-rc2 (2022-06-12 16:11:37 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git
tags/for-5.19/dm-fixes-3
for you to fetch
On Tue, 14 Jun 2022 11:09:28 +0200, Christoph Hellwig wrote:
> this series cleans up a bunch of block layer helpers related to the chunk
> size.
>
> Diffstat:
> block/blk-merge.c | 28
> block/blk.h| 13 +
> drivers/md/dm.c|
On 2022-06-17 08:56, Damien Le Moal wrote:
>>
>> So we call this function device_not_matches_zone_sectors() from
>> validate_hardware_zoned_model() for each target and we let the validate
>> succeed even if the target's zone size is different from the underlying
>> device zone size if this feature
On 2022-06-17 08:12, Damien Le Moal wrote:
>> I think this is a cleaner approach using features flag and io_hints
>> instead of messing with the revalidate zone function:
>>
>> diff --git a/drivers/md/dm-table.c b/drivers/md/dm-table.c
>> index 135c0cc190fb..c97a71e0473f 100644
>> ---
On Thu, Jun 16, 2022 at 07:05:48PM -0400, Mike Snitzer wrote:
> > + return min(q->limits.max_sectors,
> > + blk_chunk_sectors_left(offset, chunk_sectors));
> > }
>
> While you're at it, any reason not to use queue_max_sectors() here?
I'm not sure if it is a good reason, but
