From: Mark Brown <broonie@kernel•org>
To: Jens Axboe <axboe@kernel•dk>
Cc: Andrew Morton <akpm@linux-foundation•org>,
David Carlier <devnexen@gmail•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Matthew Wilcox <willy@infradead•org>
Subject: linux-next: manual merge of the block tree with the mm-stable tree
Date: Mon, 1 Jun 2026 17:58:58 +0100 [thread overview]
Message-ID: <ah26UmcBXVJMy-Cc@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1687 bytes --]
Hi all,
Today's linux-next merge of the block tree got a conflict in:
mm/page_io.c
between commit:
d590df11be0f1 ("mm/page_io: rename swap_iocb fields for clarity")
from the mm-stable tree and commit:
ca36c1aaee095 ("block: Add bvec_folio()")
from the block tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
diff --cc mm/page_io.c
index f2d8fe7fd0574,a59b73f8bdd9d..0000000000000
--- a/mm/page_io.c
+++ b/mm/page_io.c
@@@ -499,8 -489,8 +499,8 @@@ static void sio_read_complete(struct ki
int p;
if (ret == sio->len) {
- for (p = 0; p < sio->pages; p++) {
- struct folio *folio = bvec_folio(&sio->bvec[p]);
+ for (p = 0; p < sio->nr_bvecs; p++) {
- struct folio *folio = page_folio(sio->bvecs[p].bv_page);
++ struct folio *folio = bvec_folio(&sio->bvecs[p]);
count_mthp_stat(folio_order(folio), MTHP_STAT_SWPIN);
count_memcg_folio_events(folio, PSWPIN, folio_nr_pages(folio));
@@@ -509,8 -499,8 +509,8 @@@
}
count_vm_events(PSWPIN, sio->len >> PAGE_SHIFT);
} else {
- for (p = 0; p < sio->pages; p++) {
- struct folio *folio = bvec_folio(&sio->bvec[p]);
+ for (p = 0; p < sio->nr_bvecs; p++) {
- struct folio *folio = page_folio(sio->bvecs[p].bv_page);
++ struct folio *folio = bvec_folio(&sio->bvecs[p]);
folio_unlock(folio);
}
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-06-01 16:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 16:58 Mark Brown [this message]
2026-06-01 17:44 ` linux-next: manual merge of the block tree with the mm-stable tree Matthew Wilcox
-- strict thread matches above, loose matches on Subject: below --
2024-11-11 2:52 Stephen Rothwell
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=ah26UmcBXVJMy-Cc@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=akpm@linux-foundation$(echo .)org \
--cc=axboe@kernel$(echo .)dk \
--cc=devnexen@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=willy@infradead$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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