From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Matthew Wilcox <willy@infradead.org>,
David Hildenbrand <david@redhat.com>,
Li Zhijian <lizhijian@fujitsu.com>,
Sumit Garg <sumit.garg@linaro.org>
Subject: Re: [PATCH v2] intel_th: avoid using deprecated page->mapping, index fields
Date: Tue, 28 Jan 2025 17:22:53 +0000 [thread overview]
Message-ID: <442bffb8-4f3e-4d20-b1b4-0098b74c1421@lucifer.local> (raw)
In-Reply-To: <Z5kNgELpK1-zEXm4@smile.fi.intel.com>
On Tue, Jan 28, 2025 at 07:01:52PM +0200, Andy Shevchenko wrote:
> I pinged Alexander, but It will mostly have the same effect as your email.
> So, no guarantees from me (it is not my area in the kernel, I can't help
> more).
Thanks :) regardless, appreciate you pinging!
These kind of change that touches other areas of the kernel are always tricky...
>
> On Mon, Jan 27, 2025 at 06:53:23PM +0000, Lorenzo Stoakes wrote:
> > +cc some commit signers due to total lack of response here.
> >
> > Hi Alexander/anybody at intel/elsewhere who can look at this.
> >
> > These fields are deprecated and will soon be non-optionally removed, it
> > would be good to confirm this works on actual hardware before this change
> > goes in.
> >
> > So this patch is probably more urgent than you think.
> >
> > If there is a problem with maintainership in this area, MAINTAINERS should
> > be updated accordingly so I know who to contact.
>
> --
> With Best Regards,
> Andy Shevchenko
>
>
next prev parent reply other threads:[~2025-01-28 17:34 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 [this message]
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
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=442bffb8-4f3e-4d20-b1b4-0098b74c1421@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizhijian@fujitsu.com \
--cc=sumit.garg@linaro.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