public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ard Biesheuvel <ardb@kernel.org>,
	linux-mm@kvack.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mmap: remove the IA64-specific vma expansion implementation
Date: Mon, 13 Nov 2023 16:00:14 +0100	[thread overview]
Message-ID: <6df6cfaf-e704-49cd-9002-eb27b4e8369b@redhat.com> (raw)
In-Reply-To: <20231113124728.3974-1-lukas.bulwahn@gmail.com>

On 13.11.23 13:47, Lukas Bulwahn wrote:
> With commit cf8e8658100d ("arch: Remove Itanium (IA-64) architecture"),
> there is no need to keep the IA64-specific vma expansion.
> 
> Clean up the IA64-specific vma expansion implementation.
> 
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
>   mm/mmap.c | 37 +------------------------------------
>   1 file changed, 1 insertion(+), 36 deletions(-)
> 
> diff --git a/mm/mmap.c b/mm/mmap.c
> index 1971bfffcc03..72a3bdea4fa4 100644
> --- a/mm/mmap.c
> +++ b/mm/mmap.c
> @@ -2207,42 +2207,7 @@ struct vm_area_struct *find_extend_vma_locked(struct mm_struct *mm, unsigned lon
>   }
>   #endif
>   
> -/*
> - * IA64 has some horrid mapping rules: it can expand both up and down,
> - * but with various special rules.
> - *
> - * We'll get rid of this architecture eventually, so the ugliness is
> - * temporary.

Hurray

Acked-by: David Hildenbrand <david@redhat.com>

-- 
Cheers,

David / dhildenb


      reply	other threads:[~2023-11-13 15:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-13 12:47 [PATCH] mmap: remove the IA64-specific vma expansion implementation Lukas Bulwahn
2023-11-13 15:00 ` David Hildenbrand [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=6df6cfaf-e704-49cd-9002-eb27b4e8369b@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=ardb@kernel.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lukas.bulwahn@gmail.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