From: David Marchand <david.marchand@redhat.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>
Cc: dev@dpdk.org, Vamsi Krishna Attunuru <vattunuru@marvell.com>
Subject: Re: [PATCH v2] kni: fix build with Linux 6.3
Date: Wed, 19 Apr 2023 16:38:42 +0200 [thread overview]
Message-ID: <CAJFAV8wvG_pFx7sXQ=THbz_C1YGA402G4ey7XHOEb2_k7xcoTA@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8x4iScS0zhJEp6H3=dt0QjxvunUqjoFb3EH0+E8ZZwukQ@mail.gmail.com>
> On Fri, Apr 14, 2023 at 5:25 PM Ferruh Yigit <ferruh.yigit@amd.com> wrote:
> >
> > KNI calls `get_user_pages_remote()` API which is using `FOLL_TOUCH`
> > flag, but `FOLL_TOUCH` is no more in public headers since v6.3,
> > causing a build error.
> >
> > `FOLL_*` defines in Linux kernel first moved to another header [1],
> > later some of them moved to memory subsystem internal header [2] for 6.3
> >
> > `get_user_pages_remote()` already sets `FOLL_TOUCH` internally,
> > no need to set this flag externally anyway, moving flag from the call
> > altogether.
> >
> > [1]
> > Commit b5054174ac7c ("mm: move FOLL_* defs to mm_types.h")
> >
> > [2]
> > Commit 2c2241081f7d ("mm/gup: move private gup FOLL_ flags to internal.h")
> >
> > Signed-off-by: Ferruh Yigit <ferruh.yigit@amd.com>
>
> Reviewed-by: David Marchand <david.marchand@redhat.com>
Applied, thanks Ferruh.
--
David Marchand
prev parent reply other threads:[~2023-04-19 14:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 17:29 [PATCH] " Ferruh Yigit
2023-02-28 20:45 ` David Marchand
2023-03-20 12:10 ` David Marchand
2023-03-20 13:01 ` David Marchand
2023-03-24 3:04 ` [EXT] " Vamsi Krishna Attunuru
2023-04-13 7:22 ` David Marchand
2023-04-14 15:29 ` Ferruh Yigit
2023-04-14 15:25 ` [PATCH v2] " Ferruh Yigit
2023-04-17 7:32 ` David Marchand
2023-04-19 14:38 ` David Marchand [this message]
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='CAJFAV8wvG_pFx7sXQ=THbz_C1YGA402G4ey7XHOEb2_k7xcoTA@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=vattunuru@marvell.com \
/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).