From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Matthew Wilcox <willy@infradead.org>,
Viacheslav Dubeyko <slava@dubeyko.com>,
Ira Weiny <ira.weiny@intel.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hfsplus: Convert kmap() to kmap_local_page() in bitmap.c
Date: Mon, 01 Aug 2022 14:56:42 +0200 [thread overview]
Message-ID: <2117828.irdbgypaU6@opensuse> (raw)
In-Reply-To: <5834FD23-A333-40B7-9678-43E61986512E@dubeyko.com>
On martedì 26 luglio 2022 20:40:29 CEST Viacheslav Dubeyko wrote:
>
> > On Jul 25, 2022, at 10:54 AM, Matthew Wilcox <willy@infradead.org>
wrote:
> >
> > On Mon, Jul 25, 2022 at 10:17:13AM -0700, Viacheslav Dubeyko wrote:
> >> Looks good. Maybe, it makes sense to combine all kmap() related
modifications in HFS+ into
> >> one patchset?
> >
> > For bisection, I'd think it best to leave them separate?
>
> I am OK with any way. My point that it will be good to have patchset to
see all modified places together, from logical point of view. Even if we
have some issue with kmap() change on kmap_local_page(), then, as far as I
can see, the root of issue should be kmap_local_page() but not HFS+ code.
Oppositely, if it’s some undiscovered HFS+ issue, then again
kmap_local_page() changes nothing. But I am OK if it is separate patches
too.
>
> Thanks,
> Slava.
>
And I am OK with sending a patchset :-)
I'm sorry because, while working on the last conversions for HFS+ in
btree.c, I just noticed that I had overlooked one other kmap() call site in
bitmap.c.
Therefore, I'd like to ask to drop this patch and I'll also ask to drop the
patch to bnode.c in the related thread.
When done, I'll send a series of three patches, one per file (bnode.c,
bitmap.c, btree.c).
Thanks,
Fabio
next prev parent reply other threads:[~2022-08-01 12:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-24 20:50 [PATCH] hfsplus: Convert kmap() to kmap_local_page() in bitmap.c Fabio M. De Francesco
2022-07-25 17:17 ` Viacheslav Dubeyko
2022-07-25 17:54 ` Matthew Wilcox
2022-07-26 18:40 ` Viacheslav Dubeyko
2022-08-01 12:56 ` Fabio M. De Francesco [this message]
2022-07-26 19:11 ` Ira Weiny
2022-07-26 20:38 ` Matthew Wilcox
2022-07-26 12:04 ` Fabio M. De Francesco
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=2117828.irdbgypaU6@opensuse \
--to=fmdefrancesco@gmail.com \
--cc=ira.weiny@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=slava@dubeyko.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).