linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Biancaa Ramesh <biancaa2210329@ssn.edu.in>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Cc: Muchun Song <muchun.song@linux.dev>,
	Oscar Salvador <osalvador@suse.de>,
	David Hildenbrand <david@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] spell check: Edited spelling errors
Date: Fri, 24 Oct 2025 15:53:53 +0700	[thread overview]
Message-ID: <aPs-oaYxarodr7fg@archie.me> (raw)
In-Reply-To: <20251021173614.48249-1-biancaa2210329@ssn.edu.in>

[-- Attachment #1: Type: text/plain, Size: 3168 bytes --]

On Tue, Oct 21, 2025 at 11:06:13PM +0530, Biancaa Ramesh wrote:
> Signed-off-by: Biancaa Ramesh <biancaa2210329@ssn.edu.in>

As others have pointed out in all your previous patches: make sure to describe
your changes (in imperative mood) along with appropriate one-line patch title;
and most importantly: don't add any confidentality disclaimers.

> ---
>  mm/hugetlb.c | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> index 795ee393eac0..1760fa39a3af 100644
> --- a/mm/hugetlb.c
> +++ b/mm/hugetlb.c
> @@ -2934,7 +2934,7 @@ typedef enum {
>  	 * NOTE: This is mostly identical to MAP_CHG_NEEDED, except
>  	 * that currently vma_needs_reservation() has an unwanted side
>  	 * effect to either use end() or commit() to complete the
> -	 * transaction.	 Hence it needs to differenciate from NEEDED.
> +	 * transaction.	 Hence it needs to differentiate from NEEDED.
>  	 */
>  	MAP_CHG_ENFORCED = 2,
>  } map_chg_state;
> @@ -5983,7 +5983,7 @@ void __unmap_hugepage_range(struct mmu_gather *tlb, struct vm_area_struct *vma,
>  			int rc = vma_needs_reservation(h, vma, address);
>  
>  			if (rc < 0)
> -				/* Pressumably allocate_file_region_entries failed
> +				/* Presumably allocate_file_region_entries failed
>  				 * to allocate a file_region struct. Clear
>  				 * hugetlb_restore_reserve so that global reserve
>  				 * count will not be incremented by free_huge_folio.
> @@ -6007,7 +6007,7 @@ void __unmap_hugepage_range(struct mmu_gather *tlb, struct vm_area_struct *vma,
>  	/*
>  	 * If we unshared PMDs, the TLB flush was not recorded in mmu_gather. We
>  	 * could defer the flush until now, since by holding i_mmap_rwsem we
> -	 * guaranteed that the last refernece would not be dropped. But we must
> +	 * guaranteed that the last reference would not be dropped. But we must
>  	 * do the flushing before we return, as otherwise i_mmap_rwsem will be
>  	 * dropped and the last reference to the shared PMDs page might be
>  	 * dropped as well.
> @@ -6211,7 +6211,7 @@ static vm_fault_t hugetlb_wp(struct vm_fault *vmf)
>  	 * In order to determine where this is a COW on a MAP_PRIVATE mapping it
>  	 * is enough to check whether the old_folio is anonymous. This means that
>  	 * the reserve for this address was consumed. If reserves were used, a
> -	 * partial faulted mapping at the fime of fork() could consume its reserves
> +	 * partial faulted mapping at the time of fork() could consume its reserves
>  	 * on COW instead of the full address range.
>  	 */
>  	if (is_vma_resv_set(vma, HPAGE_RESV_OWNER) &&
> @@ -7193,7 +7193,7 @@ long hugetlb_change_protection(struct vm_area_struct *vma,
>  		} else if (unlikely(is_pte_marker(pte))) {
>  			/*
>  			 * Do nothing on a poison marker; page is
> -			 * corrupted, permissons do not apply.  Here
> +			 * corrupted, permissions do not apply.  Here
>  			 * pte_marker_uffd_wp()==true implies !poison
>  			 * because they're mutual exclusive.
>  			 */

The wording itself LGTM, though.

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

           reply	other threads:[~2025-10-24  8:54 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20251021173614.48249-1-biancaa2210329@ssn.edu.in>]

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=aPs-oaYxarodr7fg@archie.me \
    --to=bagasdotme@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=biancaa2210329@ssn.edu.in \
    --cc=david@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=muchun.song@linux.dev \
    --cc=osalvador@suse.de \
    /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).