From: Luis Chamberlain <mcgrof@kernel.org>
To: axboe@kernel.dk, agk@redhat.com, snitzer@kernel.org,
philipp.reisner@linbit.com, lars.ellenberg@linbit.com,
christoph.boehmwalder@linbit.com, hch@infradead.org,
djwong@kernel.org, minchan@kernel.org, senozhatsky@chromium.org
Cc: patches@lists.linux.dev, linux-block@vger.kernel.org,
linux-mm@kvack.org, linux-xfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, dm-devel@redhat.com,
drbd-dev@lists.linbit.com, linux-kernel@vger.kernel.org,
willy@infradead.org, hare@suse.de, p.raghav@samsung.com,
da.gomez@samsung.com, rohan.puri@samsung.com,
rpuri.linux@gmail.com, kbusch@kernel.org, mcgrof@kernel.org
Subject: [PATCH v3 0/4] block: simplify with PAGE_SECTORS_SHIFT
Date: Fri, 15 Sep 2023 15:43:39 -0700 [thread overview]
Message-ID: <20230915224343.2740317-1-mcgrof@kernel.org> (raw)
Just spinning these low hanging fruit patches I forgot about.
Changes on v3:
o Add tags for Reviews/acks
o rebase onto next-20230914
o Fixes as suggested by Johannes Thumshirn:
- drop not-needed parens on dm bufio
- use SECTOR_MASK instead of PAGE_SECTORS - 1 for the zram driver
o Drop shmem patches as they are already merged / modified
Changes on v2:
o keep iomap math visibly simple
o Add tags for Reviews/acks
o rebase onto next-20230525
Luis Chamberlain (4):
drbd: use PAGE_SECTORS_SHIFT and PAGE_SECTORS
iomap: simplify iomap_init() with PAGE_SECTORS
dm bufio: simplify by using PAGE_SECTORS_SHIFT
zram: use generic PAGE_SECTORS and PAGE_SECTORS_SHIFT
drivers/block/drbd/drbd_bitmap.c | 4 ++--
drivers/block/zram/zram_drv.c | 15 ++++++---------
drivers/block/zram/zram_drv.h | 2 --
drivers/md/dm-bufio.c | 4 ++--
fs/iomap/buffered-io.c | 2 +-
5 files changed, 11 insertions(+), 16 deletions(-)
--
2.39.2
WARNING: multiple messages have this Message-ID (diff)
From: Luis Chamberlain <mcgrof@kernel.org>
To: axboe@kernel.dk, agk@redhat.com, snitzer@kernel.org,
philipp.reisner@linbit.com, lars.ellenberg@linbit.com,
christoph.boehmwalder@linbit.com, hch@infradead.org,
djwong@kernel.org, minchan@kernel.org, senozhatsky@chromium.org
Cc: p.raghav@samsung.com, linux-xfs@vger.kernel.org,
rohan.puri@samsung.com, da.gomez@samsung.com, mcgrof@kernel.org,
patches@lists.linux.dev, willy@infradead.org,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
linux-mm@kvack.org, dm-devel@redhat.com,
linux-fsdevel@vger.kernel.org, rpuri.linux@gmail.com,
kbusch@kernel.org, drbd-dev@lists.linbit.com
Subject: [dm-devel] [PATCH v3 0/4] block: simplify with PAGE_SECTORS_SHIFT
Date: Fri, 15 Sep 2023 15:43:39 -0700 [thread overview]
Message-ID: <20230915224343.2740317-1-mcgrof@kernel.org> (raw)
Just spinning these low hanging fruit patches I forgot about.
Changes on v3:
o Add tags for Reviews/acks
o rebase onto next-20230914
o Fixes as suggested by Johannes Thumshirn:
- drop not-needed parens on dm bufio
- use SECTOR_MASK instead of PAGE_SECTORS - 1 for the zram driver
o Drop shmem patches as they are already merged / modified
Changes on v2:
o keep iomap math visibly simple
o Add tags for Reviews/acks
o rebase onto next-20230525
Luis Chamberlain (4):
drbd: use PAGE_SECTORS_SHIFT and PAGE_SECTORS
iomap: simplify iomap_init() with PAGE_SECTORS
dm bufio: simplify by using PAGE_SECTORS_SHIFT
zram: use generic PAGE_SECTORS and PAGE_SECTORS_SHIFT
drivers/block/drbd/drbd_bitmap.c | 4 ++--
drivers/block/zram/zram_drv.c | 15 ++++++---------
drivers/block/zram/zram_drv.h | 2 --
drivers/md/dm-bufio.c | 4 ++--
fs/iomap/buffered-io.c | 2 +-
5 files changed, 11 insertions(+), 16 deletions(-)
--
2.39.2
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
next reply other threads:[~2023-09-15 22:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 22:43 Luis Chamberlain [this message]
2023-09-15 22:43 ` [dm-devel] [PATCH v3 0/4] block: simplify with PAGE_SECTORS_SHIFT Luis Chamberlain
2023-09-15 22:43 ` [PATCH v3 1/4] drbd: use PAGE_SECTORS_SHIFT and PAGE_SECTORS Luis Chamberlain
2023-09-15 22:43 ` [dm-devel] " Luis Chamberlain
2023-09-15 22:43 ` [PATCH v3 2/4] iomap: simplify iomap_init() with PAGE_SECTORS Luis Chamberlain
2023-09-15 22:43 ` [dm-devel] " Luis Chamberlain
2023-09-18 5:53 ` Johannes Thumshirn
2023-09-18 5:53 ` [dm-devel] " Johannes Thumshirn
2023-09-15 22:43 ` [PATCH v3 3/4] dm bufio: simplify by using PAGE_SECTORS_SHIFT Luis Chamberlain
2023-09-15 22:43 ` [dm-devel] " Luis Chamberlain
2023-09-18 5:54 ` Johannes Thumshirn
2023-09-18 5:54 ` [dm-devel] " Johannes Thumshirn
2023-09-15 22:43 ` [PATCH v3 4/4] zram: use generic PAGE_SECTORS and PAGE_SECTORS_SHIFT Luis Chamberlain
2023-09-15 22:43 ` [dm-devel] " Luis Chamberlain
2023-09-18 5:55 ` Johannes Thumshirn
2023-09-18 5:55 ` [dm-devel] " Johannes Thumshirn
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=20230915224343.2740317-1-mcgrof@kernel.org \
--to=mcgrof@kernel.org \
--cc=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=christoph.boehmwalder@linbit.com \
--cc=da.gomez@samsung.com \
--cc=djwong@kernel.org \
--cc=dm-devel@redhat.com \
--cc=drbd-dev@lists.linbit.com \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=kbusch@kernel.org \
--cc=lars.ellenberg@linbit.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=p.raghav@samsung.com \
--cc=patches@lists.linux.dev \
--cc=philipp.reisner@linbit.com \
--cc=rohan.puri@samsung.com \
--cc=rpuri.linux@gmail.com \
--cc=senozhatsky@chromium.org \
--cc=snitzer@kernel.org \
--cc=willy@infradead.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.