linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ignacio Moreno Gonzalez <Ignacio.MorenoGonzalez@kuka.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"Liam R. Howlett" <Liam.Howlett@oracle.com>,
	yang@os.amperecomputing.com, willy@infradead.org,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: madvise: make MADV_NOHUGEPAGE a no-op if !THP
Date: Wed, 14 May 2025 17:59:23 +0200	[thread overview]
Message-ID: <b12548c7-9f1c-48bc-a728-d169fcd5e16f@kuka.com> (raw)
In-Reply-To: <42872c96-e9c5-4c3c-9095-3f12202dd803@lucifer.local>

On 5/14/2025 5:27 PM, Lorenzo Stoakes wrote:

>> On 5/14/2025 3:52 PM, Lorenzo Stoakes wrote:
> 
> Igancio - you're deleting too much context here, you did it in the other email
> too, it's really hard to follow what's going on. Please try to be careful about
> what bits of an email you delete when quoting.
> 
> You're putting my comment here without the context of what I asked Andrew, so
> now it's not clear what's going on.
> 

Hi Lorenzo,

Sorry about that and thanks for letting me know. I appreciate your advice, since I am new in the mailing list. I will try to include more context to avoid confusion in the future :)


>>> I have pinged s390 people on there, but I don't think this is going to make this
>>> cycle given we will probably need to coordinate with them to fix up this enum
>>> name (which seems the best solution to me!...)
>>
>> They answered that it would be ok for them to do a quick fix over the mm tree:
>>
>> https://lore.kernel.org/linux-mm/6f8f3780-902b-49d4-a766-ea2e1a8f85ea@linux.ibm.com/
> 
> Yeah, we need to figure out who's going to do this patch though :)
> 
> Did you want to Iganacio?
> 
> I would suggest chasing up with them to see if they plan to do it or you ought
> to do so.
> 
> I can also do it if you need it quick, but I don't want to deprive you of the
> opportunity to patch that :)

For me it's fine if you create the patch. That will probably be faster ;)


  reply	other threads:[~2025-05-14 15:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-08 10:20 Ignacio Moreno Gonzalez via B4 Relay
2025-05-08 11:49 ` Lorenzo Stoakes
2025-05-08 15:06 ` David Hildenbrand
2025-05-08 15:32 ` Yang Shi
2025-05-08 19:04 ` Liam R. Howlett
2025-05-09  5:47   ` Ignacio Moreno Gonzalez
2025-05-09 17:24     ` Liam R. Howlett
2025-05-14 13:52 ` Lorenzo Stoakes
2025-05-14 15:07   ` Ignacio Moreno Gonzalez
2025-05-14 15:25     ` Yang Shi
2025-05-14 15:29       ` Lorenzo Stoakes
2025-05-14 16:54         ` Yang Shi
2025-05-14 15:27     ` Lorenzo Stoakes
2025-05-14 15:59       ` Ignacio Moreno Gonzalez [this message]
2025-05-14 22:36         ` Andrew Morton
2025-05-15  5:30           ` Lorenzo Stoakes
2025-05-14 20:15 ` James Houghton
2025-05-15  7:03   ` Ignacio Moreno Gonzalez
2025-05-15 13:03     ` Lorenzo Stoakes
2025-05-15 14:42       ` Ignacio Moreno Gonzalez

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=b12548c7-9f1c-48bc-a728-d169fcd5e16f@kuka.com \
    --to=ignacio.morenogonzalez@kuka.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=willy@infradead.org \
    --cc=yang@os.amperecomputing.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