From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
Cc: Ben Hutchings <ben.hutchings@codethink.co.uk>,
Lorenzo Stoakes <lstoakes@gmail.com>,
stable@vger.kernel.org
Subject: Re: [PATCH 4.4] mm/gup: add compat macro for get_user_pages
Date: Thu, 31 Jan 2019 13:26:01 +0100 [thread overview]
Message-ID: <20190131122601.GA31839@kroah.com> (raw)
In-Reply-To: <154893372158.59047.15701214929637353941.stgit@buzz>
On Thu, Jan 31, 2019 at 02:22:01PM +0300, Konstantin Khlebnikov wrote:
> This fixes API breakage introduced in v4.4.168 commit 8e50b8b07f46
> ("mm: replace get_user_pages() write/force parameters with gup_flags").
> For example odious nvidia out-of-tree modules does not compile.
There is no guarantee of in-kernel api "stability" in any kernel tree,
sorry.
As all of the in-kernel users are working just fine, there is no need
for this type of crazy patch to be accepted.
thanks,
greg k-h
prev parent reply other threads:[~2019-01-31 12:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 11:22 [PATCH 4.4] mm/gup: add compat macro for get_user_pages Konstantin Khlebnikov
2019-01-31 12:26 ` Greg Kroah-Hartman [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=20190131122601.GA31839@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ben.hutchings@codethink.co.uk \
--cc=khlebnikov@yandex-team.ru \
--cc=lstoakes@gmail.com \
--cc=stable@vger.kernel.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).