linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	David Hildenbrand <david@redhat.com>
Subject: Re: [PATCH v2 RESEND] intel_th: avoid using deprecated page->mapping, index fields
Date: Mon, 31 Mar 2025 18:15:14 +0200	[thread overview]
Message-ID: <2025033142-rack-viewer-80d4@gregkh> (raw)
In-Reply-To: <Z-q5Gf57y9LEZcUE@casper.infradead.org>

On Mon, Mar 31, 2025 at 04:47:37PM +0100, Matthew Wilcox wrote:
> On Mon, Mar 31, 2025 at 01:56:08PM +0100, Lorenzo Stoakes wrote:
> > Greg, as we're late in merge window obviously now, could you roll up into
> > 6.15-rc1? Thanks!
> > 
> > This does not require backporting, as this is a critical change for mm
> > moving forward, as page->index,mapping are deprecated and will be entirely
> > removed extremely soon.
> 
> "extremely soon" as in "There are four places in the kernel which
> currently use page->index, and three of them are gone once Andrew
> sends his pull requests".  So this will be the last user, assuming
> nobody else decides to add a user of page->index in the meantime.

I'll get to it after -rc1 is out, thanks.

greg k-h


  reply	other threads:[~2025-03-31 16:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-31 12:56 [PATCH v2 RESEND] intel_th: avoid using deprecated page->mapping, index fields Lorenzo Stoakes
2025-03-31 15:47 ` Matthew Wilcox
2025-03-31 16:15   ` Greg Kroah-Hartman [this message]
2025-04-14 14:33     ` Matthew Wilcox
2025-04-15 11:29       ` Greg Kroah-Hartman
2025-04-15 11:34         ` Lorenzo Stoakes

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=2025033142-rack-viewer-80d4@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=david@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.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).