From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Matthew Wilcox <willy@infradead.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
David Hildenbrand <david@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v2] intel_th: avoid using deprecated page->mapping, index fields
Date: Mon, 31 Mar 2025 12:59:36 +0100 [thread overview]
Message-ID: <3a98bce9-7508-4ab5-b2c0-2493d2256c53@lucifer.local> (raw)
In-Reply-To: <87frityadj.fsf@ubik.fi.intel.com>
+cc Greg
On Mon, Mar 31, 2025 at 09:36:40AM +0300, Alexander Shishkin wrote:
> Matthew Wilcox <willy@infradead.org> writes:
>
> > On Wed, Jan 29, 2025 at 01:39:06PM +0200, Alexander Shishkin wrote:
> >> Lorenzo Stoakes <lorenzo.stoakes@oracle.com> writes:
> >>
> >> > Thanks very much! Yeah just keen to get this in as we are moving towards
> >> > removing these fields very soon.
> >>
> >> My understanding is that this is a part of larger effort to reduce
> >> struct page to 8 bytes and an optionally dynamically allocated slightly
> >> larger structure, is that correct? Just curious.
> >>
> >> > Could you take this in your tree? I think that'd work best.
> >>
> >> Sure, will do.
> >
> > Hi, this doesn't appear to be in linux-next yet. Could you confirm it's
> > scheduled to hit the next merge window?
>
> Yes, I'll send it to Greg once -rc1 is tagged.
Right, is this ultimately handled in Greg's PR? Did you not send to him
ready for the merge window?
Or did you? I'm confused.
We do really need this merged for 6.15, can we make sure this actually
lands? You did confirm it'd go in 2 months ago, and the patch was sent 4
months ago, and we have been chasing this repeatedly.
For reference, patch is [0].
[0]: https://lore.kernel.org/all/20241203080001.12341-1-lorenzo.stoakes@oracle.com/
>
> Regards,
> --
> Alex
Thanks, Lorenzo
next prev parent reply other threads:[~2025-03-31 15:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 8:00 Lorenzo Stoakes
2025-01-06 11:06 ` Lorenzo Stoakes
2025-01-27 18:53 ` Lorenzo Stoakes
2025-01-28 17:01 ` Andy Shevchenko
2025-01-28 17:22 ` Lorenzo Stoakes
2025-03-28 17:57 ` Lorenzo Stoakes
2025-01-29 7:57 ` Alexander Shishkin
2025-01-29 9:22 ` Lorenzo Stoakes
2025-01-29 11:39 ` Alexander Shishkin
2025-01-29 11:51 ` Lorenzo Stoakes
2025-02-21 17:40 ` Lorenzo Stoakes
2025-03-04 21:08 ` Matthew Wilcox
2025-03-31 6:36 ` Alexander Shishkin
2025-03-31 11:59 ` Lorenzo Stoakes [this message]
2025-03-31 12:01 ` Greg Kroah-Hartman
2025-03-31 12:08 ` Lorenzo Stoakes
2025-03-31 12:39 ` Greg Kroah-Hartman
2025-03-31 13:02 ` Lorenzo Stoakes
2025-03-31 12:31 ` Matthew Wilcox
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=3a98bce9-7508-4ab5-b2c0-2493d2256c53@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=david@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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